request_user_bind
Starts a user consent binding. Withauth_type=sms the gateway sends a verification code to the phone number; with auth_type=h5 it returns an authorization link (minisite) where the user signs in to grant access. Neither mode returns a grant immediately — call verify_user_bind to complete it.
Binding flow (entry point):
request_user_bind → get bind_id (sms) or request_id + h5_url (h5) → user enters the code / opens the link to authorize → verify_user_bind exchanges it for a consent_grant_id → subsequent business tools carry that consent_grant_id. This is the first step of the auth flow and is a binding tool: it only requires the Agent identity (connection layer Authorization: Bearer clw_) and has no consent_grant_id parameter.Parameters
Returns
The return shape depends onauth_type.
auth_type=sms:
auth_type=h5:
Error Codes
See Error Handling for the full list.

