Update White Label
Path parameters
Headers
Request
Updated comma-separated list of allowed domains for OAuth flows.
Response
Human-readable name for the white label integration. This helps you identify the integration in the UI and should clearly describe its purpose (e.g., ‘Customer Portal Slack Integration’, ‘Enterprise Google Drive Access’).
Technical identifier of the source type that this integration supports (e.g., ‘slack’, ‘google_drive’, ‘github’). This determines which service provider the OAuth integration connects to.
OAuth2 client secret from your registered application. This is used to securely authenticate your application when exchanging authorization codes for access tokens. Keep this value secure and never expose it in client-side code.
Comma-separated list of allowed domains for OAuth flows and CORS. This prevents unauthorized websites from using your OAuth credentials and should include all domains where your application is hosted.
Identifier of the organization that owns this white label integration. White label integrations are isolated per organization for security and multi-tenancy.
Timestamp when the white label integration was created (ISO 8601 format).
Timestamp when the white label integration was last modified (ISO 8601 format).