Update push registration

PUT

/push

Last modified:2026-10-03 07:43:29

OperationId:UpdatePushConfigurationSystem

Changes the push service, sandbox setting, or device of an existing registration anywhere on the platform. The registration is found by push-device-token, which is required and cannot itself be changed. To replace a token, register the new one with POST, which removes the old one.

Who can call it:

Super User updates any registration.

Reseller updates registrations in domains of its territory.

Every other scope gets 403. Use PUT /domains/{domain}/users/{user}/push for your own.

The token must be a registration you can manage. A token that is not registered, or whose registration is outside your reach, returns 404. The registration keeps its owner: domain and user in the body never move it. A new push-device must be another device of the same user.

Answers 202. The change is accepted and applied shortly after, so a read made straight after it can still show the previous state.

Request

Authorization

Bearer Token

Provide your bearer token in the

Authorization

header when making requests to protected resources.

Example:

Authorization: Bearer ********************

Body Params application/jsonRequired

Examples

Responses

🟢202Accepted

application/json

Accepted; applied shortly after.

Bodyapplication/json

🟠400Bad Request

🟠401Unauthorized

🟠403Forbidden

🟠404Not Found

🔴503Service Unavailable

Request Example

Shell

JavaScript

Java

Swift

curl --location --request PUT 'https://awqacore01.crexendocloud.com/ns-api/v2/push' \
--header 'Authorization: Bearer <token>' \
--header 'Content-Type: application/json' \
--data '{
    "push-device-token": "a1b2c3d4e5f60718293a4b5c6d7e8f90a1b2c3d4e5f60718293a4b5c6d7e8f90",
    "push-network": "apns",
    "push-test": "yes"
}'

Response Example

202 - Accepted

Accepted; applied shortly after.

{
    "code": 202,
    "message": "Accepted"
}

Modified at 2026-10-03 07:43:29

Unregister push device