Beazley Authentication
Every Beazley API is fronted by Azure API Management and secured with an APIM subscription key. The key travels either in the Ocp-Apim-Subscription-Key request header or as a subscription-key query parameter; both schemes are declared in all fourteen published OpenAPI documents and both are accepted at the top level of every operation. There is no OAuth 2.0, no OpenID Connect and no mutual TLS anywhere on the public surface: neither /.well-known/openid-configuration nor /.well-known/oauth-authorization-server is served on any Beazley host.
Beazley secures its APIs with apiKey across 2 declared security schemes, as derived from its OpenAPI definitions.
Security Schemes
Source
Authentication Profile
Work with this as data
Every security artifact here is available over the APIs.io API and to AI agents over MCP.