Dunning as infrastructure for your product
A complete REST API v1, webhooks signed both ways, OpenAPI spec and Postman collection. Your system creates the charges; the engine handles the rest — with end-to-end idempotency.
Everything you need to integrate
From api-key to your first charge in the workflow
Create the person, create the charge and link it to a workflow. From there, the workflow follows the charge on its own: it notifies, offers an agreement, pauses on exceptions and closes out when payment arrives.
# Create a person
curl -X POST https://app.dunning.kobana.com.br/api/v1/people \
-H "Authorization: Bearer YOUR_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"name": "Empresa Exemplo Ltda",
"document": "12345678000190",
"email": "financeiro@exemplo.com.br"
}'
# Create a charge linked to a workflow
curl -X POST https://app.dunning.kobana.com.br/api/v1/charges \
-H "Authorization: Bearer YOUR_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"person_id": "per_123",
"amount": 450.00,
"due_date": "2026-08-15",
"collection_rule_id": "rule_456"
}'Receive events in your system
Configure outbound endpoints and receive workflow events — charge paid, agreement accepted, dispute opened, notification delivered — with a verifiable signature.
- ✓HMAC signature on every delivery
- ✓Secret rotation:
POST /v1/webhook-endpoints/{id}/rotate-secret - ✓Queryable delivery history
Send payment events
In standalone mode, record payment signals with evidence and a confidence level — the engine stops the workflow instantly.
# Create a webhook endpoint
curl -X POST https://app.dunning.kobana.com.br/api/v1/webhook-endpoints \
-H "Authorization: Bearer YOUR_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"url": "https://seusistema.com.br/webhooks/dunning",
"events": ["charge.paid", "agreement.accepted", "dispute.opened"]
}'
Integration flow
From your Kobana account to telemetry in 6 steps.
Security at every layer
From authentication to audit, everything is built for collections operations that need to prove every step.
- ✓OAuth2 Kobana: unified identity with the platform
- ✓Revocable api-keys: control by key and workspace
- ✓Signed webhooks: HMAC with secret rotation
- ✓Rate limiting: protection on sensitive endpoints (portal and identity verification)
- ✓Immutable audit log: append-only, enforced by Postgres, queryable via the API
- ✓Portal tokens: stored only as a SHA-256 hash
Frequently asked questions
Ready to bring the workflow into your product?
Schedule a demo and see the API, the webhooks and the telemetry working with a full portfolio scenario.