Oauth Providers

AdminUpdated Sep 11, 2026

Dashboard API — authenticated by an Atlas console (platform-instance) session, not a key.

7 routes. Each row is one endpoint with its explanation and whether it honours the Idempotency-Key header.

Method & path	Idem	Explanation
`GET /v1/dashboard/accounts/:accountId/instances/:instanceId/oauth_providers`		The whole provider catalog with per-instance state and the redirect URI to register.
`PUT /v1/dashboard/accounts/:accountId/instances/:instanceId/oauth_providers/:provider`		Store a client id and secret. Write-only: no route ever returns the secret.
`DELETE /v1/dashboard/accounts/:accountId/instances/:instanceId/oauth_providers/:provider`		Forget the credentials. Linked accounts are preserved (E17).
`POST /v1/dashboard/accounts/:accountId/instances/:instanceId/oauth_providers/:provider/enabled`		Enable or disable a configured provider without deleting anyone identity.
`POST /v1/dashboard/accounts/:accountId/instances/:instanceId/oauth_providers/:provider/scope`		Scope a provider to sign-in, sign-up, or both. Enforced at the resolver.
`POST /v1/dashboard/accounts/:accountId/instances/:instanceId/oauth_providers/:provider/shared_keys`		Opt in or out of Atlas shared development credentials. Refused for production.
`POST /v1/dashboard/accounts/:accountId/instances/:instanceId/oauth_providers/:provider/test`		Probe the provider token endpoint to check the client id and secret only.

Was this page helpful?