Build and operate without relying on a black box.
Sandbox, observability, applications, automations, and contract tests run on Achadu itself and use the same API source of truth.
Contracts and downloads
OpenAPI 3.1
Complete specification with 121 operations, schemes, scopes and errors.
Download or open →↗Postman Collection
Collection generated from the same catalog, ready to import and use variables.
Download or open →↗Achadu CLI
Official lightweight terminal client, CI and universal API access.
Download or open →Postman
Import the collection, create an Environment and define base_url and api_key. The folders follow the same domains as the public reference.
base_url=https://achadu.com/api/v1
api_key=ach_live_...Bruno
In Bruno, choose Import Collection, select OpenAPI and enter the URL below. The client creates the 121 requests maintaining parameters and example bodies.
https://achadu.com/api/v1/openapi.jsonIsolated sandbox per account
ach_test keys use data separate from production. You can change the examples and restore the environment without touching actual offers, groups, recipe, or webhooks.
Offer, coupon, group, segment, template and demonstrative publication.
The same routes, validations, pagination and scopes as production.
One-hour, one-day or seven-day credentials.
One click recreates the initial test state.
curl https://achadu.com/api/v1/offers \
-H "Authorization: Bearer ach_test_..."Observability by credential
The center shows volume, success rate, average latency, errors and recent requests for each key. CSV preserves request_id, route, status, and duration for auditing.
Apps and temporary tokens
Register an application to the account, choose the allowed scopes, and exchange Client ID and Client Secret for a one-hour Bearer token. Revoking the application terminates all tokens issued to it.
curl -X POST https://achadu.com/api/developer/oauth/token \
-H "Content-Type: application/json" \
-d '{"client_id":"ach_app_...","client_secret":"ach_secret_...","scope":"offers:read analytics:read"}'Automations library
Native recipes combine required trigger, actions, and scopes. Every installation starts as a draft and only runs after explicit activation.
Preview and publication in chosen destinations.
Editorial update of the showcase.
Attribution of high-intent conversations.
Combined reading of publication, audience and revenue.
Contract tests on the panel itself
Validation checks names, routes, methods, scopes, webhook versions, domains, and sandbox isolation. Each execution is recorded with duration and result.