Partner portal

How to notify an external system the instant something happens here. You subscribe an address to an event, and the platform starts calling it — with a trail of each delivery.

The tenant registers an ENDPOINT (a URL of yours) to be NOTIFIED over HTTP every time a business event happens in Tenka — contract signed, document paid, FCA opened. Each notification is a POST signed with HMAC-SHA256 of the body using a SECRET that only you and Tenka know (header X-Tenka-Signature): your system verifies the signature and knows the call came from Tenka and was not tampered with. Here you create the subscription (url + event + secret), activate/deactivate it, follow the delivery TRAIL (PENDING → DELIVERED | FAILED, with the number of attempts and the backoff), and can trigger a TEST event or requeue a delivery that failed. The "*" event subscribes to all. Distinct from the internal billing webhooks (Asaas).

Each delivery is signed with the subscription's secret. The receiver MUST verify this signature before trusting the content — without it, anyone who discovers your URL can send a fake event to it.

The test button sends a real event to your endpoint right now, without waiting for the fact to happen. It is the fastest way to discover a URL, firewall or signature error — before the first real event gets lost in the queue.

A API pública /api/v1 é congelada: nada some nem muda de tipo; mudança que quebra vai para /v2. O SDK sai do próprio contrato: /api/v1/sdk/tenka.js e /api/v1/sdk/tenka.py. O histórico de versões está no documento API-CHANGELOG da Biblioteca.

An endpoint that is down does not lose the event: the platform tries again, spacing out the attempts. The trail shows the status and how many attempts there were — that is where you find out that the integration "stopped" because the certificate on the other side expired.

O log de eventos mostra tudo que a conta enviou, em todas as inscrições, com filtro por evento e situação. Reenviar cria uma entrega nova com o mesmo conteúdo e o cabeçalho X-Tenka-Replay-Of com o id da original, para o sistema que recebe não duplicar. Toda entrega leva X-Tenka-Event-Version com a versão do contrato.

Which of my systems does Tenka notify when something happens — and are the deliveries arriving? Register an endpoint (a URL of yours) per business event and Tenka sends a POST signed with HMAC-SHA256 of the body (header X-Tenka-Signature), which your system verifies to know the call came from here and was not tampered with. The delivery trail shows PENDING, DELIVERED or FAILED, with the number of attempts and the backoff; you can trigger a test event and requeue a delivery that failed. The * event subscribes the endpoint to all events.