en/api/openapi.yaml, the English version of api/openapi.yaml). All paths are relative to the proposed base URL: https://api.t3sa.com/v1 in production or https://sandbox.api.t3sa.com/v1 in the sandbox. Neither is live yet.
Resource paths, field names, event names and error codes are in Portuguese by design and are the same in every language of this documentation.
Every request carries Authorization: Bearer <key>. State-changing requests accept Idempotency-Key and, in the current proposal, the optional HMAC signature with Tesa-Timestamp and Tesa-Signature. See Authentication.
Organization
Wallets
Positions
Allocation policy
Proposals
Redemptions
Records
Yield and charges
Webhooks
No endpoint receives a private key or a signed transaction. After approval, the transactions go to the company or its custodian, which signs and broadcasts them. TESA tracks the on-chain confirmation and updates the status.