# 2023 October ## :tada: Major updates ### *Milestone feature*: reworked authorization header :tada: We made **direct authorization** to the provider endpoints possible. Providers can now use the `authorization` header to expect tokens directly from consumers. The token from the initial gateway login will then use the new `x-apx-authorization` header instead. \ This *does not break existing subscriptions*, consumption can also be carried on using the original authorization header. ### Further feature releases * We added a **step-by-step guide for subscribers** how to consume subscribed services. The Technical Setup section of your subscriptions now shows the necessary steps to make a successful API call, along with dynamically generated cURL examples. * The interface now supports **multiple currencies** for the pricing of plans. Tenant administrators can define in the Admin Area which currencies should be available for all workspaces. * It is now possible to **delete APIs** from your API collection, as long as they are not assigned to any live plan. * Administrators can now see the **list of users** for every workspace in their tenant. ## :tools: Improvements & fixes * The Workspace Users list now also shows the email address for each user. * The parser for uploaded APIs will now give you more detailed error descriptions. * Improved the workspace selection drop-down by pinning the active workspace to the top of the list, and included a direct link to manage the users of the active workspace. * Increased character limit for API keys used as Consumer Clients. * Fixed the mail delivery of subscription approval requests to providers. * ...and many more. --- # 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.apinity.io/release-notes/2023-october.md?ask= ``` 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.