PATCH
cURL

Authorizations

Authorization
string
header
required

JWT bearer token. App-user tokens are issued by POST /auth/token (the partner backend calls it as its platform service account); admin and dashboard tokens are issued via OIDC login.

Path Parameters

user_id
string
required

User ID

Body

application/json
address

A user-submitted address as captured: either the structured form, a single free-text string, or both (the original text plus whatever was structured from it). #[serde(untagged)] keeps the wire shape natural — a bare object or a bare string — so existing structured clients are unaffected.

raw is Secret because a free-text address is PII (it embeds the same data masked elsewhere as line1 / pincode).

dob
string | null
Example:

"2000-01-15"

email
string | null
first_name
string | null
gender
null | enum<string>

User gender.

Available options:
MALE,
FEMALE,
OTHER
id_proof
null | object
last_name
string | null
occupation
null | enum<string>

Occupation of a user. Stored as TEXT — deliberately not a PostgreSQL enum, so adding a value needs no migration.

Available options:
DRIVER,
HOUSEKEEPING_STAFF,
SECURITY

Response

User updated; access_token is present only for an app-user caller

user
object
required
access_token
string | null

A freshly minted app token, carrying the updated identity claims. Present only when the caller is the app user themselves; absent for dashboard / service callers, which hold no app token to refresh.