POST /remotes/push/e2ee/register
Register a push device to bouncer to receive end-to-end encrypted mobile push notifications.
Self-hosted servers use this endpoint to asynchronously register a push device to the bouncer server after receiving a request from the mobile client to register E2EE push device.
It is not meant to be used by mobile clients directly.
Changes: New in Zulip 11.0 (feature level 406).
Servers
- https://{subdomain}.zulipchat.com/api/v1
- {server}/api/v1
- https://chat.zulip.org/api/v1
Request headers
| Name | Type | Required | Description |
|---|---|---|---|
Content-Type |
String | Yes |
The media type of the request body.
Default value: "application/x-www-form-urlencoded" |
Request body fields
| Name | Type | Required | Description |
|---|---|---|---|
token_id |
String | Yes |
The Changes: New in Zulip 12.0 (feature level 468),
replacing |
bouncer_public_key |
String | Yes |
The |
realm_uuid |
String | Yes |
The UUID of the realm to which the push device being registered belongs. |
encrypted_push_registration |
String | Yes |
The |
How to start integrating
- Add HTTP Task to your workflow definition.
- Search for the API you want to integrate with and click on the name.
- This loads the API reference documentation and prepares the Http request settings.
- Click Test request to test run your request to the API and see the API's response.