Enable Membership Integration
enable Membership Integration.
A membership integration connects an external identity provider (Google, Facebook, Apple, Azure AD, and others) so your users can sign in with it. Provider secrets are configured in the dashboard.
Enables the membership integration.
JWT Bearer Authorization
Integration id, from get_membership_integrations.
The CodeMash API version used to fetch data from the API. If not specified, the last version will be used. E.g.: v3
EnableMembershipIntegrationRequest
ID of your project. Can be passed in a header as norbix-project-id.
Target environment for this request (e.g. TEST, STAGING). Optional — when omitted the request runs against PROD. Can be passed in a header as norbix-env.
Specify culture code when your response from the API should be localised. E.g.: en
TimeZone
CorrelationId for each request
OK
PUT /{version}/membership/integrations/{Id}/enable HTTP/1.1
Host: hub.norbix.ai
Authorization: Bearer YOUR_SECRET_TOKEN
Content-Type: multipart/form-data
Accept: */*
Content-Length: 142
{
"projectId": "text",
"env": "text",
"resolvedEnv": {
"value": "text",
"isProd": true
},
"cultureCode": "text",
"timeZoneId": "text",
"correlationId": "text"
}OK
{
"responseStatus": {
"isSuccess": true
}
}In the dashboard
Manage this visually in Norbix Cloud — see Membership → Integrations.
Use it from code
Every Norbix SDK exposes this endpoint as a method — see Enable Membership Integration in the SDK reference, with examples in every language.
Last updated