> For the complete documentation index, see [llms.txt](https://docs.frends.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.frends.com/api-portal/api-portal.md).

# API Portal

Frends API Portal is a comprehensive, self-service developer portal designed for publishing and managing APIs created in the Frends integration platform.

This portal allows Frends customers and partners to securely expose their Frends-built APIs to their own developers, customers, and end-users. It provides a fully-featured, white-label-ready environment where users can discover available APIs, explore interactive documentation, test endpoints directly in the browser, and manage their subscriptions and API keys.

<figure><img src="https://1296181907-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fkld7XwlsZKJMSV4KMD07%2Fuploads%2FQ84hkfoJtml77uUbK9zb%2Fimage.png?alt=media&amp;token=17b395ff-735b-4e12-8256-45c260090249" alt=""><figcaption></figcaption></figure>

By offering a professional and branded self-service experience, the API Portal accelerates the adoption of your APIs, fosters a vibrant developer community, and unlocks new business opportunities by turning your integrations into reusable products.

In order to get started with API Portal and obtain it for your organisation, please contact Frends Sales.

Check out the demo here to for introduction to API Portal:

{% @storylane/embed subdomain="app" linkValue="w5jrduk2f50s" url="<https://app.storylane.io/share/w5jrduk2f50s>" %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

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

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.frends.com/api-portal/api-portal.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.