---
title: "Confirm Connection"
method: POST
path: "/vault/connections/{unified_api}/{service_id}/confirm"
tags: ["Connections"]
---

# Confirm Connection

`POST /vault/connections/{unified_api}/{service_id}/confirm`

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.

## Path parameters

- `service_id` string, required
- `unified_api` string, required

## Headers

- `x-apideck-consumer-id` string, required
- `x-apideck-app-id` string, required

## Request body

- ConfirmConnection
  - `confirm_token` string, required — The confirm token received from the OAuth callback redirect.

## Response `200`

Connection confirmed

- ConfirmConnectionResponse
  - `status_code` integer, required — HTTP Response Status Code
  - `status` string, required — HTTP Response Status
  - `data` object, required
    - `confirmed` boolean, required

## Other responses

- `400` — Bad Request
- `401` — Unauthorized
- `402` — Payment Required
- `404` — The specified resource was not found
- `422` — Unprocessable
- `default` — Unexpected error

---

[API](https://skmtc.net/apideck-libraries/apis/vault-api.md) · [All operations](https://skmtc.net/apideck-libraries/apis/vault-api/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/apideck-libraries/vault-api/versions/1b8e8b6feb36/schema)
