Skip to main content
Connecting a user is the first step of Issuing. You send them a one-time code, they read it back, and you receive their user.id. Your server names the user with that id when it creates and manages their cards. Every call on this page is made by your server with your org token as the bearer (see step 1 of the Quickstart).

Send the user a code

By email or phone. external_user_id is optional: your own id for the user, returned on webhooks so you can match them up.

Verify the code

In sandbox the code is always 111111.
Store user.id. It is how your server names the user on /api/v2 calls, always with your org token. The connection.created webhook fires here. Once per user, before you create their first card:

Refresh the connection

The card endpoints don’t need the access_token, so you can skip this step if your server does everything. If you also connect an agent to the MCP server, its token expires after one hour. Rotate it with the refresh token, using your org token as the bearer:
Each refresh returns a new pair and invalidates the old one. Store what comes back. An invalid_refresh_token means it was already used or expired: reconnect the user.

Users you know by phone only

Sandbox

Sandbox sends email but not SMS, and the code is always 111111. Sandbox users are isolated: connecting anyone@example.com in sandbox can never touch a real account.