SuperdindaDocs
Admin

What happened to one seat

GET
/admin/seats/{uid}/timeline

Consent, pairing, sync and subscription in one order. The cursor carries the instant, the source and the id together, because consent and pairing routinely write in the same millisecond and an instant alone would repeat or skip a row at a page boundary.

Authorization

Bearer
headerAuthorizationBearer <JWT>

Path Parameters

uid*string
Length1 <= length

Query Parameters

cursor?string
limit?integer
Range1 <= value <= 200

Response Body

The timeline

application/json
  1. response
success*true
Value intrue
data*
Example Request
curl -X GET 'http://localhost:3000/admin/seats/string/timeline'
Example Response
{  "success": true,  "data": {    "events": [      {        "at": "string",        "source": "consent",        "kind": "string",        "detail": "string"      }    ],    "nextCursor": "string"  }}

One customer, in full GET

A dependent appears as a FIRST NAME, an age band, and a masked phone and document. Enough for support to talk about a person, never enough to be a lookup key; the full phone or document only through POST /admin/seats/{uid}/reveal, with a reason.

People with an account GET

Next Page