Token export
Export one active connection's credentials through an authenticated, audited request.
Token export hands out a live credential. The current implementation exports one active connection at a time. Direct users can export their own connections; business owners and administrators can export connections in their authorized project. Ordinary execution API keys and MCP agent tokens cannot export credentials.
The authenticated management endpoint is:
POST /v1/orgs/{orgId}/projects/{projectId}/connections/{connectionId}/exportIt is served by the API runtime and requires the current browser session and trusted app
origin. Responses carry Cache-Control: no-store, and successful exports create an audit
event before returning credentials. The endpoint is rate limited.
The response includes connectionId, app, scopes, expiresAt, accessSource,
accessToken and, when available, refreshToken. The source and credential method distinguish OAuth from imported API-key or basic credentials. OAuth client secrets and Arc0 supplier
credentials are not included. Bulk organization exports are not implemented.
Imported API keys and basic credentials remain live at their provider after Arc0 removes its stored copy. Revoke those credentials at the provider when required; Arc0 reports provider revocation as unconfirmed. Basic credentials are encoded, not rendered as a password field, in an export.
Portability
For customer-owned OAuth, you retain the client credentials needed by the provider's refresh flow. For Arc0-managed OAuth, exporting a refresh token does not also export Arc0's client secret; continued refresh can require Arc0. Actual token lifetime and refresh behavior depend on the provider.
Export does not revoke the connection. Store exported credentials in your secret manager, and use the connection's revoke control when you intend to retire it. Avoid copying credentials into agent prompts, logs, support tickets or source control.
See OAuth apps for how the connection's OAuth configuration is bound.