SDK Token Issuance

Request — POST {base_url}/h5/oauth/token

Prebook token (raw passenger identity):

{
    "partner_name": "Partner Name",
    "partner_key": "Partner Key",
    "email": "jane.doe@example.com",
    "phone": "+123212321",
    "first_name": "Jane",
    "last_name": "Doe",
    "salutation": "Ms"
}

Ride Hailing token — same shape, but the partner_name and partner_key values are replaced with the ride hailing equivalent

Responses

On 200, The returned access_token is what the host passes to the SDK as token / rhToken.

Notes

onSessionInvalid

is debounced: a burst of 401s fires the host exactly once (sessionInvalidFired in callbacks.ts) until a new token is set.

• Runtime refresh without remount:handle.updateSession(ses) and handle.setRhToken(token) swap tokens in place; the SDK keeps running.

onLogout

vs

onExit

: logout clears the session and is host-owned; exit leaves the session intact and just returns the user to the host UI.

• The SDK never authenticates a user. No password, OTP, or OAuth flow lives in the SDK — minting ses/rhToken is entirely the host/partner backend’s job