Skip to main content

errand_verify_user_bind

Verifies the SMS code and establishes the user authorization, returning a consent_grant_id. This is the closing step of the errand authorization flow and only needs the Agent credential — it does not take a consent_grant_id parameter.
Errand authorization flow (closing step): errand_request_user_bind → get bind_id → user receives the code → errand_verify_user_bind exchanges it for a consent_grant_id → subsequent errand tools carry that consent_grant_id.
Errand’s consent_grant_id is independent from delivery’s: the consent_grant_id minted here works only for errand tools — a delivery consent_grant_id cannot call errand tools. Only customers with cross-capability sharing enabled get one consent_grant_id that works for both errand and delivery (and revoking it then revokes both — see revoked_scopes on the errand_revoke_user_bind page). Re-binding the same phone number rotates the grant: a new consent_grant_id is issued and the old one is invalidated immediately.

Parameters

Returns

Error Codes

See Error Handling for the full list. Typical latency: ~0.5s.

Call Example