Push
List a push message's deliveries
GET/v1/push/messages/{id}/deliveries
Requires an API key with the messages:read scope. About keys and scopes
What each device answered for one push message (id from the send). A push reaches every ready installation of the contact, so a message has one delivery per device. accepted: Apple, Google or the browser's push service took it, which is not proof the device showed it. invalid: the device is gone and its installation was retired. rejected: refused, often the app's key or a payload the provider would not take. retryable: will be tried again. unknown: the provider may have taken it, so it is not resent. skipped: not attempted, as when the app's key was refused for another device of the same app. pending and started are still in flight. A message that is not a push answers 404.
Path parameters
idstringrequireduuid
Query parameters
limitintegeroptionalmin > 0 · max 100 · default
20cursorstringoptional1–2048 characters
Returns
Returns 200 OK with a list of PushDelivery objects in data, and the next page's cursor in meta (see pagination). Otherwise returns an error; Errors lists every code and which to retry.
idstringrequireduuid
installationIdstringrequiredThe device the delivery went to.
uuid
platformstringrequiredone of
ios,android,webstatusstringrequiredone of
pending,started,accepted,invalid,rejected,retryable,unknown,skippedattemptCountintegerrequiredTimes sending was tried.
min 0 · max 9007199254740991
startedAtstring | nullrequiredWhen the first attempt began.
date-time
resolvedAtstring | nullrequiredWhen it reached a final status.
date-time
createdAtstringrequireddate-time