/ Docs
APIPush registrations

Revoke Push Devices

Stop pushes to registrations using their revocation secrets. Idempotent.

POST
/v1/public/push-registrations/revoke

Authorization

BearerAuth
AuthorizationBearer <token>

Botyard API key — see /docs/authentication.

In: header

Request Body

application/json

TypeScript Definitions

Use the request body type in TypeScript.

Revoke registrations by their secrets (no session required).

Response Body

curl -X POST "https://example.com/v1/public/push-registrations/revoke" \  -H "Content-Type: application/json" \  -d '{    "revocations": [      {        "registration_id": "string",        "revocation_secret": "stringstringstri"      }    ]  }'
Empty
{
  "type": "string",
  "title": "string",
  "status": 0,
  "detail": "string",
  "instance": "string",
  "error_code": "string",
  "errors": [
    {
      "pointer": "string",
      "detail": "string",
      "type": "string"
    }
  ],
  "trace_id": "string"
}

Issue Push Content Keys

Mint (or rotate) content keys for some of the caller's active registrations. All-or-nothing: if any id is not one of the caller's active registrations, nothing changes and the request is a 404.

Search Push Content

Read what the banners of pushed notifications may show, with a content key. A wrong key, or a registration that is unknown, disabled or has no key, is a 404. Otherwise each requested notification is either in ``items`` or left out.