# Authorization Header update

> We updated the authorization scheme in our API to better align with OpenAPI specifications.

Published Feb 21, 2024

Product: EDI platform

We updated the authorization scheme in our API to better align with OpenAPI specifications.

The `Authorization` header no longer requires the `Key` prefix. Instead, you should now provide API keys directly (`Authorization ${STEDI_API_KEY}`). This change aligns with the OpenAPI standard and allows for out-of-the-box compatibility with OpenAPI tools and services.

Previously, our APIs required API keys to be passed with a `Key` prefix (`Authorization: Key ${STEDI_API_KEY}`), which required manual setup to work with OpenAPI. We will continue to support the previous format for backward compatibility, but we encourage you to adopt the new format to leverage the benefits of OpenAPI compliance.