---
title: "Verify connected account user"
method: POST
path: "/api/v1/connected_accounts/user/verify"
tags: ["Connected Accounts"]
---

# Verify connected account user

`POST /api/v1/connected_accounts/user/verify`

Confirms the user assertion and activates the connected account after the user completes third-party OAuth. Called by the B2B app server with auth_request_id and identifier. Validates that the asserted identifier matches the one stored on the auth request and promotes pending tokens to live.

## Request body

- ConnectedAccountsVerifyConnectedAccountUserRequest
  - `auth_request_id` string, required — Auth request ID as base64url-encoded opaque token from the user verify redirect URL query params
  - `identifier` string, required — Current logged in user's connected account identifier

## Response `200`

Verification successful; connected account is now ACTIVE

- ConnectedAccountsVerifyConnectedAccountUserResponse
  - `post_user_verify_redirect_url` string — URL to redirect the user to after successful verification

## Other responses

- `400` — Invalid request - missing or malformed fields
- `401` — Unauthorized - invalid or missing access token
- `403` — Forbidden - identifier mismatch
- `404` — Not found - no pending flow for the given auth_request_id or already consumed

---

[API](https://skmtc.net/scalekit/apis/scalekit-api-reference.md) · [All operations](https://skmtc.net/scalekit/apis/scalekit-api-reference/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/scalekit/scalekit-api-reference/versions/a40d5d4650e5/schema)