POST
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
required

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).

bank_details
object
required

Origin-bank details required to open a purpose-bound account at PBA.

dob
string
required
Example:

"2000-01-15"

first_name
string
required
gender
enum<string>
required

User gender.

Available options:
MALE,
FEMALE,
OTHER
last_name
string
required
salutation
enum<string>
required

Title or honorific for a person.

Available options:
MR,
MRS,
MS,
MASTER
email
string | null

Response

Onboarding completed

access_token
string
required
user
object
required