"user": "~", or your own domain and user. Without them the request gets 403.403.push-device is required and must be an existing device within your reach. Any other answers 404 with Device not found. Below Reseller it must be your own device.push-device-token, that registration is removed. The token must be registered on that device, or the request returns 404. A token that is not registered at all is treated as already removed.push-device-token, the registrations stay and only the device's push delivery is switched off.apns_chat token, which covers chat only and leaves call notifications on.push-network pwa, every web push registration of the user named by domain and user is removed instead, and push-device is not needed. Send both, or "user": "~" for your own; without them the request returns 400. The answer is {"response": "ok"} with no device.202 with {"response": "ok", "device": ...}. The change is accepted and applied shortly after, so a read made straight after it can still show the previous state.Authorization: Bearer ********************curl --location --request DELETE 'https://awqacore01.crexendocloud.com/ns-api/v2/push' \
--header 'Authorization: Bearer <token>' \
--header 'Content-Type: application/json' \
--data-raw '{
"user": "~",
"push-device": "sip:1001a@example.com",
"push-device-token": "a1b2c3d4e5f60718293a4b5c6d7e8f90a1b2c3d4e5f60718293a4b5c6d7e8f90",
"push-network": "apns"
}'{
"response": "ok",
"device": "sip:1001a@example.com"
}