---
title: "Get a pairing token/QR to complete this request on a phone"
method: GET
path: "/auth/{requestId}/pairing"
tags: ["Pairing"]
---

# Get a pairing token/QR to complete this request on a phone

`GET /auth/{requestId}/pairing`

## Request

- Base URL: `https://atk.tvarka.pro/v1`
- URL: `https://atk.tvarka.pro/v1/auth/{requestId}/pairing`
- Auth: HTTP basic

Only for `method:"nfc"`. Basic only - the integrator's server rotates the one-time token.
Returns a high-entropy, short-lived, one-claim pairing token and a deep link / QR the phone
scans. The phone then calls `/pairing/claim`, receives the request's `clientToken`, and
drives the same `/certificate` + `/complete` endpoints.

## Path parameters

- `requestId` string, uuid, required

## Response `200`

Pairing payload.

- AuthPairingInfo
  - `pairingUrl` string, uri
  - `deepLink` string
  - `qrPayload` string
  - `pairingToken` string, required: High-entropy, one-claim, short-lived.
  - `expiresAt` string, date-time, required

## Other responses

- `401`: Missing/invalid credentials or client token.
- `404`: Unknown request.
- `409`: State/idempotency conflict (spent operation token, identity swap, terminal request).

---

[API](https://skmtc.dev/tvarka/apis/tvarka-atk-api.md) · [All operations](https://skmtc.dev/tvarka/apis/tvarka-atk-api/llms.txt) · [OpenAPI document](https://skmtc.dev/tvarka/apis/tvarka-atk-api/revisions/2ab888b16069?raw)