account-access

Register a device push token

Changed on

Idempotent. A token belongs to one user: registering it from another account moves it there. Tokens are deleted when the push service reports them unregistered and when the account is deleted.

post/me/push-tokens

Request

  • Base URL: https://eu.bisibility.com/api/v1
  • URL: https://eu.bisibility.com/api/v1/me/push-tokens
  • Auth: one of:
    • HTTP bearer
    • OAuth 2 (authorization code, authorization URL /api/auth/oauth2/authorize, token URL /api/auth/oauth2/token, scopes: api:read)

Headers

Bisibility-API-Version'v1'

API contract version requested by the client. Omit this header to use the current backward-compatible behavior.

Idempotency-Keystring

Optional key that makes a retry of this request return the first response instead of running it again. Replays last 24 hours and are scoped to the credential, method and path.

X-Bisibility-Source'sdk' | 'cli' | 'mcp'

Declares the client that produced the request for usage reporting: sdk, cli or mcp. Optional; any other value counts as api. It never changes authentication or which budget applies (every bearer-authenticated request counts against the API, MCP and SDK budget).

Request body

bundle_idstring required

App bundle identifier, for example com.bisibility.app.

environment'production' | 'sandbox' required

APNs environment of the build: sandbox for development builds.

tokenstring required

APNs device token as hexadecimal.

Response

JSON response

bundle_idstring required
created_atstring date-time required
environment'production' | 'sandbox' required
idstring required
last_seen_atstring date-time required
token_suffixstring required

Last 8 characters of the token; the token itself is never returned.

Example response

{
  "id": "dpt_a00000000000000000000000"
}

Changes