Trida Platform

Shared capabilities for Trida products, behind one HTTP API and one API key per project: Core (projects, keys, secrets, signed webhooks, usage), and as they ship Notify (WhatsApp, e-mail, SMS), Pay, Billing, AI and Account.

Everything here is derived from the code: the API reference is generated from the OpenAPI contract, the error table from the error codes of the contract, and the examples are compiled and tested in the repository. Platform version 0.1.0.

Where to start

• New here? Follow Getting started: check your key, register a webhook endpoint and receive a signed event in ten minutes.
• Calling the API: Authentication, Idempotency, Errors, Limits.
• Receiving events: Webhooks.
• Trying without a real provider: Sandbox.
• In TypeScript: the SDK.
• What exists today: the capabilities pages say what is available and what is coming.

The rules that never change

• HTTP is the contract. The SDKs are generated from the OpenAPI document; you never need a shared library to use the platform.
• Every effect is idempotent, both ways: you send an Idempotency-Key on every creation, and every event carries a stable id you deduplicate on.
• Truth is at the provider. A webhook triggers a re-read by the platform; nothing changes state from a browser redirect.
• Your project is isolated by construction. One API key opens one project, never more.