push-transport

Send Test Push

post/v1/push-transport/{provider}/test

Request

  • Base URL: https://api.elaan.io (the document declares no server; this is the origin it was published from)
  • URL: https://api.elaan.io/v1/push-transport/{provider}/test
  • Auth: none declared

Path parameters

provider'fcm' | 'apns' | 'expo' | 'onesignal' | 'webpush' required

The service a push subscription is delivered through — the routing key that ties a contact's PushSubscription to the tenant's configured PushTransportConfig and selects which sender adapter delivers it.

Cross-cutting vocabulary (like Channel): it lives in shared because both contact (the destination side) and push_transport / outbound_push (the sending side) reference the same members, and they must not drift apart.

Covers direct transports (FCM / APNs / Web Push) and aggregators that fan out to the native platforms themselves (Expo, OneSignal). Subclassing str keeps JSON and dict keys clean.

Headers

authorizationstring nullable

Request body

tokenstring required
authstring nullable
p256dhstring nullable

Example request

{
  "token": "ExponentPushToken[xxxxxxxxxxxxxxxxxxxxxx]",
  "auth": "kQm...==",
  "p256dh": "BN1...=="
}

Response

Successful Response

providerstring required
ticket_idstring nullable required

Changes

No recorded changes to this operation across all 1 revision of this API.