Push registration and topic delivery
Section ID: Guide/je0koesfs2#overview
Recipient registration and topic membership describe who can receive a notification. Trigger acceptance and provider acknowledgements do not establish arrival.
Device registration presence
Section ID: Guide/je0koesfs2#device-registration
| 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
Section ID: Guide/je0koesfs2#topic-membership
Use the topic operation reference to distinguish the key you choose from the topic identifier returned by the service. Check the membership result and the per-user failure results before treating a batch as complete.
Topic delivery and retirement
Section ID: Guide/je0koesfs2#topic-sends
| Field | Behavior |
|---|---|
excludeUserId | Excludes one recipient, commonly the person who triggered the event. |
acknowledged | Indicates acceptance of the topic send. |
status | Provider acknowledgement text. 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.
Document ID: Guide/je0koesfs2