SocialProviderResponseDto
Example
JSON
{ "slug": "google", "kind": "google", "method": "google", "display_name": "string", "client_id": "string", "client_secret_set": false, "apple_team_id": "string", "apple_key_id": "string", "apple_private_key_set": false, "discovery_url": "string", "scopes": [ "string" ], "enabled": false, "verified_at": "2026-04-20T12:00:00.000Z", "callback_url": "https://auth.example.com/v1/identity/auth/social/google/callback", "version": 0, "created_at": "2026-04-20T12:00:00.000Z", "updated_at": "2026-04-20T12:00:00.000Z" }
Properties
The provider's name in this Environment: the kind for a named provider, the developer's own name for a custom one.
The sign-in method the provider adds while enabled: the kind, or `oidc:<slug>` for a custom provider. An organization's policy names it in `allowed_sign_in_methods`.
What a custom provider's sign-in button says; null for a named provider.
When a test sign-in through a custom provider last completed. A custom provider can be enabled only while this is set.
The redirect URI to register with the provider for this Environment's sign-ins.
Tell us how we can improve this guide.