Skip to main content
1Password uses the OAuth 2.0 authorization code flow (RFC 6749) with PKCE (RFC 7636), plus an integration key delivered in the callback fragment. Connect a user walks through the flow.

Origins

The development environment, b5dev.eu, can’t show approval prompts with current 1Password app builds. Test on production.

Scopes

Request both scopes, space-delimited:

Authorize

Called from the person’s browser. No version prefix.

Callback

The query string can also include iss and base_url.

Token

Called from your backend. Authenticate with HTTP Basic only. Sending client_id in the body as well returns 400 invalid_request.

Exchange a code

Refresh

Response

string
Bearer token for extension calls and revocation. Expires after expires_in seconds: 15 minutes.
string
Use once to get a new access token. Each refresh returns a new refresh token and invalidates the old one.
string
The person’s user ID. Can be present in newer deployments.
Treat both token strings as opaque.

Errors

Revoke

Called from your backend. Ends the person’s entire connection to your integration: the consent, the tokens, and the integration key. The access token identifies the connection, so the body is empty. See Disconnect a user.