Typed requests
Keep recipient, sender, content and message intent explicit in every API call.
DEVELOPERS
A message API with a visible state machine.
One request, structured events, clear errors and the tooling to move from sandbox to production with confidence.
A developer surface that makes the state machine visible. Move from first request to production traffic with predictable APIs, useful errors and tools built for debugging.
Open a sandboxPOST /v1/messages200 OK
curl https://api.jando.io/v1/messages -H "Authorization: Bearer ..." -d '{"to":"+14155550123","type":"otp"}'
message_idmsg_2048
RESTAPI contract
p95latency visibility
7core event states
24/7webhook replay window
01 / API CONTRACT
Small surface. Clear state machine.
Keep the request simple and make the response useful. Every field should help a developer decide what happens next.
01
Create a workspace
Generate sandbox credentials, set a callback URL and define the team members who can inspect traffic.
02
Send a test
Use a minimal request, receive a stable message ID and inspect validation before carrier delivery.
03
Consume events
Verify signatures, persist event IDs and make your handler idempotent before enabling production traffic.
04
Promote safely
Register senders, set limits, compare traces and switch credentials without changing your product contract.
02 / EVENT STREAM
Events your systems can trust.
01message.accepted+42ms
02message.screened+282ms
03message.sent+522ms
04message.delivered+762ms
HANDLER RULE
Persist the ID. Verify the signature. Make retries safe.
Your webhook consumer should be boring. The trace should carry the complexity.
03 / TOOLING MAP
Everything you need to move from test to traffic.
Safe retries
Use idempotency keys and error categories to retry only what is recoverable.
Webhook security
Verify signatures, replay events and isolate failed consumers.
SDK-ready patterns
Use familiar REST and JSON conventions that fit existing service stacks.
Trace inspector
Inspect every transition from request acceptance to carrier receipt.
Release controls
Promote configuration with limits, approvals and a production checklist.
04 / BUILD QUESTIONS
Remove uncertainty before production.
How long does the first integration take?
A basic sandbox send can be completed with one API request. Production readiness depends on sender registration, webhook handling and your internal approval process.
Are webhook events retryable?
Yes. Events have stable IDs and can be replayed so consumers can recover without requesting a new message.
What happens when an API request fails?
The response identifies whether the issue is validation, authorization, policy, provider or a temporary upstream condition.
Can engineering and support see the same trace?
Yes, with role-based access. Teams share the message ID while seeing only the fields allowed for their workspace role.
05 / NEXT BUILD