Push registration and topic delivery
Recipient registration and topic membership describe who can receive a notification. Trigger acceptance and provider acknowledgements do not establish arrival.
Device registration presence
| Response condition | Interpretation |
|---|---|
A channel omits registered and credentialCount | It has no registered credentials. Check the intended signed-in user and current device token. |
remainingCredentialCount is present after removal | Its positive value counts credentials still registered for other devices. |
Follow enrollment recovery before retrying a test notice. Confirming registration does not establish delivery.
Topic identity and membership results
| Field | Meaning |
|---|---|
topicKey | Customer-chosen identifier used to address the topic. |
topicId | Opaque topic reference returned by the API. |
isSubscribed | Omitted when false. |
failed and errors | Per-user membership failures. A partial failure does not fail the whole request. |
Topic delivery and retirement
| Field | Behavior |
|---|---|
excludeUserId | Excludes one recipient, commonly the person who triggered the event. |
acknowledged | Indicates acceptance of the topic send. |
status | Provider acknowledgement text, or "done" when the provider supplies none. Do not treat it as a closed set of delivery states. |
Deleting a topic returns an operation result in status. Its acknowledgement reports the deletion outcome; provider text defaults to done when no text is supplied. Stop future triggers and handle pending notifications separately when retiring a topic. See delete topic.