push-device-token. Requires Reseller or Super User scope to update another user's registration; every other scope except the read-only ones updates only its own and must send user with its own user or ~. To replace a token, register the new one with POST, which removes the old one.Authorization: Bearer ********************curl --location --request PUT 'https://awqacore01.crexendocloud.com/ns-api/v2/domains//push' \
--header 'Authorization: Bearer <token>' \
--header 'Content-Type: application/json' \
--data '{
"user": "1001",
"push-device-token": "a1b2c3d4e5f60718293a4b5c6d7e8f90a1b2c3d4e5f60718293a4b5c6d7e8f90",
"push-network": "apns",
"push-test": "yes"
}'{
"code": 202,
"message": "Accepted"
}