Usage-based pricing and client-defined rules
- Pricing: TESA now charges as software, by API call volume. Standard plan by monthly call tiers; Enterprise with negotiated volume and a dedicated SLA. Nothing is charged on balance, yield or principal.
GET /organizacao:taxa_sobre_rendimentoremoved;limite_chamadas_mesandchamadas_mes_atualadded.GET /rendimento:taxa_percentual,taxa_valorandrendimento_liquidoremoved;rendimento_brutorenamed torendimento_total. Yield is informational only.GET /cobrancas: now lists API usage invoices (periodo,plano,chamadas,valor,status), with thefat_prefix. Paths are unchanged.- Webhook
cobranca.emitidarenamed tofatura.emitida. - Allocation policy: no preselected allocation. The company defines the proportions and the rebalancing rules (
regras, withgatilhoandlimite). TESA does not recommend allocations. - Proposals:
origemchanges fromtesa/clientetoregra(generated by a rule in the company’s policy) andmanual, with the newregra_idfield. Thealocacao.propostaevent now means a rule in your policy generated a transaction.
Initial draft
- First public version of the API proposal, with no live endpoints yet.
- Resources: organization, wallets, positions, allocation policy, proposals, redemptions, records, yield, charges and webhooks.
- Bearer key authentication, with optional HMAC signing and
Idempotency-Key. - OpenAPI 3.1 specification published in the API reference.