Depersonalize push instance
You can depersonalize a device to detach it from a current person profile so that the device won’t receive messages when targeted by any of the person attributes
Please log in to see full path URL. Learn why.
post
/people/2/contactInformation/push/{pushRegId}/depersonalize
Authorizations:
Request rate limit:
30 requests / second (per account)
path Parameters
| pushRegId required | string Registration identifier of a particular push device registration |
header Parameters
| AppCode required | string Application code |
Responses
200
OK
400
Bad request
401
Unauthorized
403
Forbidden
404
Not Found
429
Too Many Requests
500
Internal Server Error
Response samples
- 400
- 401
- 403
- 404
- 429
- 500
Content type
application/json
Example
You will get this error response if AppCode header is missing from the request
You will get this error response if AppCode header is missing from the request
Copy
Collapse all {- "errorCode": 48001,
- "errorMessage": "Application code missing"
}
Need assistance
Encountering issues
What's new? Check out
Unsure about a term? See
Service status'%3E %3Cpath d='M11.9047 8.47667L19.3513 0H17.5873L11.1187 7.35867L5.956 0H0L7.80867 11.1287L0 20.0167H1.764L8.59067 12.244L14.044 20.0167H20M2.40067 1.30267H5.11067L17.586 18.778H14.8753' fill='%23424B5C'/%3E %3C/g%3E %3Cdefs%3E %3CclipPath id='clip0_3438_1744'%3E %3Crect width='20' height='20.0167' fill='white'/%3E %3C/clipPath%3E %3C/defs%3E %3C/svg%3E)
