user with their own user (or ~). Without it they get 403.push-device-token is a credential. It is returned in clear only to the registration's own user. Every other caller gets it masked: a long token shows only its first 2 and last 2 characters. A Super User gets it in clear by adding include-secrets=yes, and every such read is logged.limit (default 100, at most 1,000) and start. An empty result is []. For the devices alone, without tokens, add /list to the path.Authorization: Bearer ********************curl --location 'https://awqacore01.crexendocloud.com/ns-api/v2/domains//push?push-device=sip%3A1001a%40example.com&push-network=apns&limit=undefined&start=undefined&sort=push-device%20asc&user=1001&push-device-token=a1b2c3d4e5f60718293a4b5c6d7e8f90a1b2c3d4e5f60718293a4b5c6d7e8f90&push-test=no&include-secrets=yes' \
--header 'Authorization: Bearer <token>'[
{
"push-device-token": "a1************************************************************90",
"domain": "example.com",
"user": "1001",
"push-device": "sip:1001a@example.com",
"push-network": "apns",
"push-test": "no"
},
{
"push-device-token": "dE***********************************************************************************************00",
"domain": "example.com",
"user": "1002",
"push-device": "sip:1002a@example.com",
"push-network": "firebase",
"push-test": "no"
}
]