Skip to main content
POST
Recognize a caller

Authorizations

Authorization
string
header
required

Bearer authentication header of the form Bearer <token>, where <token> is your auth token.

Body

application/json

The wire contracts.

One name per concept. One card shape everywhere. Every response echoes your own identifiers, so reconciling a payment never needs a second call.

caller_phone
string
required

E.164. The body is the ONLY place this lives: a header carried no cryptographic guarantee (it is unsigned, so it is safer only against the model, not against a caller), and one value in two places is an ambiguity every consumer has to reason about.

Response

Success.

consumer
object | null
known
boolean