Get User Preferences
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.
This endpoint returns the user preferences defined in your project.
JWT Bearer Authorization
The CodeMash API version used to fetch data from the API. If not specified, the last version will be used. E.g.: v3
Id of the user whose preferences to fetch, from get_users.
Database integration id. Optional — defaults to the project's default integration.
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
GET /{version}/membership/auth/{id}/preferences?Id=text HTTP/1.1
Host: api.norbix.ai
Authorization: Bearer YOUR_SECRET_TOKEN
norbix-project-id: text
Accept: */*
OK
{
"responseStatus": {
"isSuccess": true
},
"preferences": {
"blockAllMarketingMessages": true,
"blockedTags": {},
"blockReasons": []
}
}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 Get User Preferences in the SDK reference, with examples in every language.
Last updated