Create a project
Separate environments and ownership before your first production request.
DEVELOPERS
The shortest path from product event to customer signal.
Triy APIs are designed to be readable, testable, and useful from the first integration.
TRIY / QUICKSTART
A build flow that respects your team
Triy APIs are designed to be readable, testable, and useful from the first integration.
POST /api/v1/messages
{
"channel": "sms",
"to": "+1 415 555 0123",
"body": "Your code is 482901"
}
{
"channel": "sms",
"to": "+1 415 555 0123",
"body": "Your code is 482901"
}
TRIY / INTEGRATION FLOW
A build flow that respects your team
Send a test
Use a clear payload and inspect the response without setting up a large system.
Subscribe to events
Receive delivery and verification outcomes through webhooks you control.
Harden for launch
Rotate keys, define retries, and monitor the signals that matter.
TRIY / API PRINCIPLES
Practical by design
Triy APIs are designed to be readable, testable, and useful from the first integration.
01
Readable responses
Errors carry useful messages and request IDs so debugging starts with evidence.
02
Predictable boundaries
Authentication, project access, and rate limits are explicit parts of the integration.
03
Portable workflows
Your own systems remain the source of truth; Triy delivers the communication layer.
TRIY / REFERENCE
Open API docs
Start with one request · Listen with webhooks · Keep control · Operate with context