> 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.2.md).

# API Portal Version 1.0.2

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

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

* When requesting access to an API Product, you can now add your own custom claims so the issued token carries the values to your APIs and Processes.
* Portal admins now have an easier way to grant the Portal Admin role to SSO users once they've been invited.
* The SwaggerUI page now includes a button to show the associated API Product documentation.
* A new "View SwaggerUI" button on the API Product edit page takes you directly to the SwaggerUI view.
* You can now add custom body text to the landing page under Administration -> Manage Portal Look & Feel.
* General styling improvements to the SwaggerUI page.
* Added security validation to the Swagger proxy to reject any other request that is not defined in the API specification.

## Bug Fixes <a href="#bug-fixes" id="bug-fixes"></a>

* Fixed a bug where a manually provided token was sent alongside the one generated by the portal for API specifications that mix security schemes across endpoints.
* Fixed a bug where a public access API operation would send the automatic token, resulting in a claims validation failed error.
* API specifications that include PATCH endpoints now load correctly instead of failing with an error.
* Operation server URLs and operation-level security are now resolved correctly for Swagger 2.0 specifications.
* Selecting a non-existent entity type no longer causes the filters to disappear in Audit Log tables.
* Tags in the API Product Access Control Tags dropdown now display in their original casing instead of being lowercased.


---

# 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 dynamically by asking a question.

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

```
GET https://docs.frends.com/api-portal/release-notes/api-portal-version-1.0.2.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.