> 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/release-notes/api-portal-version-1.0.4.md).

# API Portal Version 1.0.4

Released on 4th of November 2026.

This release includes the new features, improvements and bug fixes released with earlier API Portal versions.

## New Features <a href="#new-features" id="new-features"></a>

### Allow optional anonymous access to the API reference (Swagger) <a href="#allow-optional-anonymous-access-to-the-api-reference-swagger" id="allow-optional-anonymous-access-to-the-api-reference-swagger"></a>

* **How to enable:** In API Product management, open an existing API Product and go to **Details**. Under **Visibility** > **Public**, select **Allow anonymous access to Swagger** and save.
* **Which API Products:** Only public, published API Products. The option is disabled while **Private** is selected.
* **Try it out (Swagger) for visitors who are not logged in:**
  * Operations that don't require authentication can be called directly.
  * Secured operations can be called after the visitor enters their own credentials in the Swagger **Authorize** dialog.
* **Default:** Off for all API Products, including existing ones, so nothing changes until an administrator enables it.

## Improvements <a href="#improvements" id="improvements"></a>

* The request URL and curl command shown under Try it out now show the request to your API, instead of the request to the API Portal's internal proxy.


---

# 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/release-notes/api-portal-version-1.0.4.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.
