> For the complete documentation index, see [llms.txt](https://docs.apinity.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.apinity.io/release-notes/2024-may.md).

# 2024 May

## :tada: Major updates

### Milestone feature: *API status* :tada:

Providers have now the option to set **statuses on published APIs** (Operational, Degraded, Major Outage, Maintenance). Service subscribers will be informed of status changes automatically, and can thus be informed of ongoig incidents as well as planned downtimes, all within the portal UI. A status history of individual APIs, as well as a live overview of all consumed/provided APIs is also available.

### Further feature releases

* Hugely improved the portal's UI with a **center stage layout.**

## :tools: Improvements & fixes

* A new Data Insights section was introduced to the left hand menu of My Hub.
* Added notification to workspace owners if another owner deletes the workspace.
* Improved plan cancellation workflow and user experience.
* Fixed redirection when logging in from certain subpages.
* Fixed a bug with frozen Manage Plans button on Service cards under certain conditions.
* ...and many more.


---

# 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.apinity.io/release-notes/2024-may.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.