Grant Contact Consent
grant Contact Consent.
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.
Handles the contact consent.
JWT Bearer Authorization
Id of the user (contact) to grant consent for.
Delivery channel to grant consent on: Email, Sms, or Push.
The CodeMash API version used to fetch data from the API. If not specified, the last version will be used. E.g.: v3
GrantContactConsentRequest
CorrelationId for each request
Specify culture code when your response from the API should be localised. E.g.: en
TimeZone
The CodeMash API version used to fetch data from the API. If not specified, the last version will be used. E.g.: v3
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.
ID of your project. Can be passed in a header as norbix-project-id.
Lawful basis for the consent, e.g. Consent. Defaults to Consent.
Source of the consent, e.g. UserOptIn. Defaults to UserOptIn.
Optional free-text reference to evidence of consent (e.g. a form submission id).
Success
EmptyResponse
POST /{version}/membership/users/{contactId}/marketing-state/{channel}/consent HTTP/1.1
Host: api.norbix.ai
Authorization: Bearer YOUR_SECRET_TOKEN
Content-Type: multipart/form-data
Accept: */*
Content-Length: 172
{
"lawfulBasis": "text",
"source": "text",
"evidenceRef": "text",
"projectId": "text",
"env": "text",
"cultureCode": "text",
"timeZoneId": "text",
"correlationId": "text",
"version": "text"
}Success
{
"success": {
"responseStatus": {
"isSuccess": true
}
},
"responseStatus": {
"isSuccess": true
}
}In Cloud
Manage this visually in Cloud — see Membership → Users.
Use it from code
Every Norbix SDK exposes this endpoint as a method — see Grant Contact Consent in the SDK reference, with examples in every language.
Last updated
Was this helpful?