Tvarka Sign API
Machine channel for Tvarka Sign: post a document and a list of signers and Tvarka runs its ordinary qualified signing ceremony for each of them on the hosted page or in the Tvarka Sign mobile app (LT ATK over NFC, Smart-ID, Mobile-ID). Nothing in the API signs anything - a signature is always a human act with the signer's own eID - so every operation is about getting a document in front of the right person and learning what they did. Orchestration sibling of the card-level ATK API; RFC 9457 problem details, HMAC-signed webhooks, and a hosted MCP server.
Tvarka Sign 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 Digital Signature, QES, eIDAS, Lithuania, and OpenAPI. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, an API reference, authentication docs, and rate-limit docs.
This API exposes 21 operations across 15 paths, organized into 3 resource areas, and defines 14 schemas. It is described by OpenAPI 3.1.0, at version 1.2.1.
Requests are made against a single base URL, https://sign-api.tvarka.pro.
Metadata
The identity and technical contract details declared by the specification.
Authentication & Security 1
Tvarka Sign API declares
1 security scheme
for authenticating requests.
It accepts HTTP bearer tokens (bearerAuth).
By default, every request must be authenticated.
bearerAuth— Authorization: Bearer . Keys are provisioned by Tvarka during onboarding and shown once. A tsklive key acts on production; a tsktest key is the sandbox. The ke…
Paths & Operations 21
Across 15 paths, the API surfaces 21 operations — 3 DELETE, 6 GET, 2 PATCH, 10 POST. They span 3 resource areas: Signings, Batches, Files. Each is listed below with its method, path, parameters, and response codes.
Create and follow a signing.
Schemas 14
The contract defines 14 schemas that model the data the API accepts and returns. The most detailed are Signing (15 properties), Signer (15 properties), CreateSigningRequest (10 properties), StoredFile (8 properties). Each schema is shown below with its type and property counts.
Specification
The full machine-readable OpenAPI contract behind this narrative.
Source
More from Tvarka ATK API 9
Other APIs Tvarka ATK API publishes across the network.
This is an independent, third-party profile of Tvarka Sign 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.