For the complete documentation index, see llms.txt. This page is also available as Markdown.

Map Auth To User

Membership.

A contact (user) is a person in your project's membership directory, with one or more linked logins (identities). Membership manages their profile, identities, roles, and lifecycle.

Maps the auth to user.

Membership

post
Authorizations
HTTPRequired

JWT Bearer Authorization

Path parameters
userIdstringRequired
versionstring Β· nullableRequired

The CodeMash API version used to fetch data from the API. If not specified, the last version will be used. E.g.: v3

Body

Membership

authIdstringOptional
databaseIntegrationIdstring Β· nullableOptional
projectIdstringRequired

ID of your project. Can be passed in a header as norbix-project-id.

envstring Β· nullableOptional

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.

cultureCodestring Β· nullableOptional

Specify culture code when your response from the API should be localised. E.g.: en

timeZoneIdstring Β· nullableOptional

TimeZone

correlationIdstring Β· nullableOptional

CorrelationId for each request

Responses
200

OK

application/json
post/{version}/membership/users/{userId}/map-auth
200

OK

In the dashboard

Manage this visually in Norbix Cloud β€” see Membership β†’ Users.

Use it from code

Every Norbix SDK exposes this endpoint as a method β€” see Map Auth To User in the SDK reference, with examples in every language.

Last updated