Platform API Authentication
Platform API requests use a bearer credential in the Authorization header. Prefer OAuth for per-user integrations. Use a Glean-issued token for global permissions with X-Glean-ActAs, or when no OAuth path exists.
Request header
Authorization: Bearer <platform_token>
Choose an authentication method
Glean OAuth Authorization Server
Use Glean's OAuth Authorization Server for OAuth access tokens and fine-grained Glean scopes. It is enabled by default. Use DCR for approved MCP hosts. Use a static client when DCR is disabled, the application is not approved, or the application needs scopes DCR does not grant.
External IdP OAuth
Use OAuth access tokens issued by a configured identity provider such as Google, Microsoft Entra ID, Okta, or OneLogin.
Glean-issued tokens
Use user-scoped or global bearer tokens created in the Glean Admin Console. Global tokens also require X-Glean-ActAs.
Quick start
- Confirm that your application has access to the Platform API.
- For a per-user integration, obtain an OAuth access token from the Glean OAuth Authorization Server or a configured external IdP. Use a Glean-issued token for global
X-Glean-ActAs, or when no OAuth path exists. - Store the credential securely and provide it in the
Authorizationheader. - Try the Platform API Quickstart.
Platform API and Client API use the same customer-facing authentication methods. Indexing API operations use Glean-issued tokens and do not accept OAuth. Follow the method-specific setup and scope requirements for the endpoint you are calling.