How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Tvarka ATK API Pairing API

NFC remote pairing - complete a request by tapping a card on a different device.

Tvarka ATK API Pairing API is one of 10 APIs that Tvarka ATK API publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Pairing. The published artifact set on APIs.io includes an OpenAPI specification and API documentation.

This API exposes 2 operations across 2 paths, and defines 8 schemas. It is described by OpenAPI 3.2.0, at version 1.3.0.

Requests are made against a single base URL, https://atk.tvarka.pro/v1.

2 operations 2 paths 8 schemas 1 GET1 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
1.3.0
Base URL
https://atk.tvarka.pro/v1
Authentication
HTTP Basic, HTTP Bearer, API Key
Resource Areas
1

Authentication & Security 3

Tvarka ATK API Pairing API declares 3 security schemes for authenticating requests. It accepts HTTP basic authentication (basicAuth). It accepts HTTP bearer tokens (JWT) (clientToken). An API key is passed in the query as downloadToken (downloadToken). By default, every request must be authenticated.

  • basicAuth — Provider server-to-server credentials keyId:keySecret. Server-to-server only, also gated by the provider's server IP allow-list. Never placed in a browser/mobi…
  • clientToken — Short-lived, per-request JWT (ES256) minted at request creation, scoped {tenant, requestId, purpose, method, allowedOrigins}. Safe to hand to a browser/mobile…
  • downloadToken — One-off token returned with a completed sign result, for fetching the signed document.

Paths & Operations 2

Across 2 paths, the API surfaces 2 operations — 1 GET, 1 POST. Each is listed below with its method, path, parameters, and response codes.

Pairing 2

NFC remote pairing - complete a request by tapping a card on a different device.

GET
/auth/{requestId}/pairing
Get a pairing token/QR to complete this request on a phone
getAuthPairing 1 param → 200404409
POST
/pairing/claim
Claim a pairing token from the tapping phone
claimPairing body → 200404409429

Schemas 8

The contract defines 8 schemas that model the data the API accepts and returns. The most detailed are PairingClaimResponse (5 properties), ErrorBody (4 properties), PairingHint (3 properties), PairingClaimRequest (3 properties). Each schema is shown below with its type and property counts.

PairingClaimRequest
object
3 properties 1 required
ErrorBody
object
4 properties 2 required
Error
object
1 property 1 required
PairingInfo
PairingClaimResponse
object
5 properties 4 required
PairingHint
object
3 properties
ErrorCode
string
The full stable error-code catalog of the ATK API family (auth + sign + services); each endpoint returns the subset that applies to it. By HTTP status: 400 inv…
Status
string
Flat request status. Non-terminal - pending, awaitingCard, awaitingCredentials, finalizing. Terminal success - done. Terminal failure - cancelled/timeout/devic…

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

tvarka-atk-api-pairing-api-openapi.yml Raw ↑

Other APIs Tvarka ATK API publishes across the network.

Tvarka ATK API Auth API
Tvarka ATK API Erasure API
Tvarka ATK API LTV API
Tvarka ATK API Sign API
Tvarka ATK API Tvarka ATK API API
Tvarka ATK API Tvarka ATK QES Signing API (paid Tier Addendum) API
Tvarka ATK API Validation API
Tvarka ATK API Well Known API
Tvarka Sign API
Where this information came from

This is an independent, third-party profile of Tvarka ATK API Pairing API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.