TAŇBA-OOH developers
Reference and guides for public verification, the integration API, webhooks, play import, proof of play, evidence and the device protocol.
API reference
Public verification API
Live You call the platform Operations: 9
Check an approval by its number, open a structure sticker, send a complaint, read the registry of certified players and the platform status. No account needed.
Who it is for: Advertisers, operators, inspectors, journalists and anyone who has to check an approval
Evidence and offline checking
Beta You call the platform Operations: 12
The daily audit anchors, the daily seals of the received play statistics and the public ledger anchored in Bitcoin, with the proofs to check them offline with tanba-verify.
Who it is for: Auditors, operators, the authority and anyone who wants to check the records without trusting the platform
Approval envelope and revocation list formats
Beta You call the platform Operations: 2
Download the signed envelope of an approval and read the signed revocation list. The guide describes both formats.
Who it is for: Authors of players and CMS software that must refuse content without a valid approval
Integration API
Live You call the platform Operations: 41
Read approvals, structures, statistics and billing, create submissions and upload their media, and export the same data as CSV.
Who it is for: Operators, agencies and authority systems that connect their own software with an API key
Webhooks
Live The platform calls you Events: 7
The events the platform sends to your HTTPS address, with their bodies, headers and retry rules.
Who it is for: Developers who want to react to a status change, an issued or revoked approval, an offline screen or a compliance event
Play import
Live You call the platform Operations: 1
Send the plays counted by your own CMS, one row per structure, approval and hour, and get an answer for every row.
Who it is for: Operators that run their own CMS and want the platform to compare its counts with the players' reports
Proof-of-play API (tanba.pop/1)
Beta You call the platform Operations: 3
Report finished plays from a player on the certificate or the signed channel, or from a CMS in one signed batch for many players. Each record is judged on its own.
Who it is for: Authors of players and agents, and operators whose CMS reports plays for their screens
Device protocol v1
Beta You call the platform Operations: 7
How a player enrols, renews its certificate, sends heartbeats, acknowledges commands, uploads its log and reads the revocation list. Beta, while the identifiers of the signed attributes sit in a provisional arc.
Who it is for: Authors of players and of the software that runs on them, and vendors who want their player certified
Programmatic inventory and creative registry
Beta You call the platform Operations: 4
Read the screens of the market with their OpenRTB fragments and authorised sellers, and check a creative file by its hash before serving it.
Who it is for: Supply-side and demand-side platforms, trading desks and any exchange that sells or buys screens in Kazakhstan
Registered sellers (sellers.json)
Beta You call the platform Operations: 1
The public list of ad technology organisations that may be named as sellers of screens, in the IAB sellers.json format.
Who it is for: Buyers and exchanges that compare the seller chain of a bid request with the registered sellers
Open data
Beta You call the platform Operations: 4
Monthly city figures of plays and on-screen hours by district, format and daypart, as CSV and JSON with a data dictionary. Every figure passes the disclosure rules; no organisation is named.
Who it is for: Researchers, journalists, agencies and anyone who wants the market figures of the city
CMS command relay
Beta You call the platform Operations: 2
Fetch the signed commands addressed to the structures a CMS installation serves, and acknowledge each one.
Who it is for: Vendors of a CMS that is certified against the TAŇBA-OOH profile and the operators that run it
Programmatic claims and verification
Beta You call the platform Operations: 2
Tell the registry which plays an exchange says it served, and get back for every line what the players proved: matched, over-claimed or unmatched.
Who it is for: Supply-side platforms and trading desks that bill buyers on delivered plays
Guides
Getting started
The three ways to connect, the hosts they use, and a first call.
Authentication and API keys
Create a key, choose its scopes, send it, and know what a key can never do.
Webhook signatures
Verify that a delivery came from the platform, handle retries and duplicates.
Connecting a CMS
What a certified CMS must do, how it receives the signed cut-off commands, and where it reports plays.
Play import
Report the plays counted by your own CMS, hour by hour, and read the answer row by row.
Send proof of play from your players or CMS
Choose a channel, build a batch of records, sign it and send it with curl or Python, and read the answer.
Read a statement and check its evidence
Read the lines and the basis of a statement, then check the daily seal, the ledger and the approvals offline.
Submit a creative for approval
Fill in the form, send the submission, follow its states, answer a question and load the approved file and its signature onto the players.
Enrol a player
Issue a one-time token in the console, see what the player does with it and check that the player is online.
Find a statement and its evidence in the console
Open a period, create a statement, download the evidence pack of a line or of the statement and check it with tanba-verify.
Answer a violation case
Find your cases and your compliance score, read a case, know when the window to answer is open and send the answer with files.
Approval envelope and revocation list formats
What the signed envelope and the revocation list contain, the identifiers they use and what a player does with them.
Downloads
The tanba-verify checker for Linux, macOS and Windows, with SHA-256 hashes and how to check them.
Versioning and deprecation policy
What carries a version, which changes never break you, and how long a removal is announced.
Changelog
Every change to the published contract since 2026-10-06, newest first.