Device protocol v1
Beta You call the platform
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
- Base address
/d/ https://devices.tanba-ooh.kz- Contract version
1.0.0
Related guides
- Enrol a player
- Send proof of play from your players or CMS
- Approval envelope and revocation list formats
- Downloads
Download the OpenAPI file (openapi.yaml)
Operations
| Method | Path | Summary |
|---|---|---|
| POST | /d/v1/enroll | Enrol a device with a one-time token and a certificate request |
| POST | /d/v1/heartbeat | Device heartbeat (client certificate, signed body) |
| POST | /d/v1/renew | Renew the client certificate (current certificate, signed body with a new certificate request) |
| POST | /d/v1/logs | Hash-chained log segment, in answer to an audit_export command |
| POST | /d/v1/commands/{id}/ack | Acknowledge a signed command |
| GET | /d/v1/revocations/latest | Newest revocation list for devices |
| GET | /d/v1/revocations/{version} | One revocation list by version |