Confirm a mobile push route challenge

POST https://z.u1v.ru/api/v1/mobile_push/routes/challenge

Confirm ownership of a challenged UnifiedPush route.

Usage examples

The -u line implements HTTP Basic authentication. See the Authorization header documentation for how to get those credentials for Zulip users and bots.

curl -sSX POST https://z.u1v.ru/api/v1/mobile_push/routes/challenge \
    -u EMAIL_ADDRESS:API_KEY \
    --data-urlencode route_id=17 \
    --data-urlencode device_instance_id=device-1 \
    --data-urlencode challenge=0123456789abcdef0123456789abcdef

Parameters

route_id integer required

Example: 17

Server-issued push route identifier.


device_instance_id string required

Example: "device-1"

Stable application device identifier.


challenge string required

Example: "0123456789abcdef0123456789abcdef"

Challenge value delivered through the provider route.


Response

Example response(s)

Successful response from a UCS extension endpoint. Endpoint-specific fields are returned alongside the standard Zulip success envelope.

{
    "msg": "",
    "result": "success"
}