Sign in
Connections

Confirm Connection

Confirms an OAuth connection after the callback by verifying the confirm token.

This is the second step of the CSRF-protected OAuth flow. When you initiate authorization with a nonce (and CSRF protection is enabled for your account), the connection is created in an unconfirmed, non-callable state and the callback redirect returns a confirm_token in its hash fragment. Call this endpoint with that confirm_token to confirm the connection and make it callable. The confirm_token is single-use and expires 30 minutes after the callback. If you do not supply a nonce during authorization, the connection is confirmed automatically and you do not need to call this endpoint.

post/vault/connections/{unified_api}/{service_id}/confirm

Path parameters

service_idstring required

Service ID of the resource to return

unified_apistring required

Unified API

Headers

x-apideck-consumer-idstring required

ID of the consumer which you want to get or push data from

x-apideck-app-idstring required

The ID of your Unify application

Request body

confirm_tokenstring required

The confirm token received from the OAuth callback redirect.

Example request

{
  "confirm_token": "550e8400-e29b-41d4-a716-446655440000"
}

Response

Connection confirmed

status_codeinteger required

HTTP Response Status Code

statusstring required

HTTP Response Status

Example response

{
  "status_code": 200,
  "status": "OK"
}

Changes

Changed in 2 of the 68 revisions of this API.11