# API Management

Frends includes built-in API management features that you can easily use to create and manage your APIs. With the provided tools, you can create an API using OpenAPI specification, link a Process into each endpoint and then, using our low-code Process Editor, create the logic behind each endpoint. Alternatively, the APIs can be specified as passthrough APIs, where Frends will connect the public endpoint in Frends to another API endpoint in your target system.

<figure><img src="/files/eVQfohldJJrgMdFtKmlg" alt=""><figcaption><p>API Management view in Frends.</p></figcaption></figure>

The provided monitoring tools will give you wide access to checking and filtering the logs for incoming requests for each Environment. If, and when, you want to limit who can access your APIs, our powerful API Policies provide a plethora of settings that you can use to authenticate and authorize callers to your endpoints. And finally, to get a word out that you have a new API, the API Portal will show your users exactly what your API can do.

## API Specification

The API Management page in Control Panel is the central management view for all of your APIs. From here, you can create new APIs by providing an OpenAPI specification for it, and then creating a new Process or linking an existing Process to each endpoint you have specified in the spec.&#x20;

<figure><img src="/files/0SljuOXfcVOamSPwUGak" alt=""><figcaption><p>OpenAPI specification editor to create or edit an API.</p></figcaption></figure>

To learn more about creating APIs with Frends, head over to [How to create an API with Frends](/guides/api-management/how-to-create-an-api-with-frends.md).

## Passthrough APIs

Passthrough APIs allow you to forward requests from the Frends API endpoints to your system's provided APIs, in the case where data conversion or other logic is not needed. They are excellent to use to keep a coherence in your API branding, having all used endpoints within the same domain, without requiring much configuration or overhead from creating a Process in between where nothing really happens.

<figure><img src="/files/0VrC4wfnUugH4DbCu4qP" alt=""><figcaption><p>Passthrough API creation view.</p></figcaption></figure>

Read more at [Passthrough APIs](/frends-development/api-management/passthrough-apis.md) page.

## API Policies

API Policies are used to authenticate API callers with API keys or OAuth bearer token, as well as to manage the logging and throttling options for the endpoints.

<figure><img src="/files/MhJRIqbqkbEYT6hKSrWA" alt=""><figcaption><p>API Policy for setting up API key authentication.</p></figcaption></figure>

API Policies allow you to define the targeted API endpoints that the policy applies to. It can also target the endpoints through implicit wildcard if only the beginning of a URL is specified.

[Read more about API Policies here](/frends-development/api-management/api-policies.md).

## API Monitoring

In order to monitor what is happening with your Frends APIs, the **API Monitoring** page shows you all the connections made into your tenant, and what happened with them.

<figure><img src="/files/qTrBFowhaVzutG8tyLl6" alt=""><figcaption><p>API logs in Frends API Management.</p></figcaption></figure>

You can easily filter the log by API operation, status code of the response, and what method was used, to figure out what is happening. The logs include events for all requests made against your tenant, and not only the specified API endpoints, so you can also see all the unsolicited attempts made against your environment.


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.frends.com/frends-development/api-management.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
