Update a push configuration (system scope)

PUT

/push

Last modified:2026-08-21 17:26:10

OperationId:UpdatePushConfigurationSystem

Update an existing push registration.

Keyed on push-device-token alone — the path domain/user do not narrow the row that is written. Publish-only, as for create; the answer is 202 Accepted, not the updated record.

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

Update published to the mobile_events service bus.

Bodyapplication/json

🟠400Bad Request

🟠401Unauthorized

🟠403Forbidden

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-raw '{
    "push-device-token": "a1b2c3d4e5f6...",
    "push-device": "1001a@example.com",
    "domain": "example.com",
    "user": "1001",
    "push-network": "firebase",
    "push-test": "yes"
}'

Response Example

202 - Example 1

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

Modified at 2026-08-21 17:26:10

Unregister a push configuration (system scope)