Why webhook‑triggered tests?
Part of Avido’s secret sauce is that you can kick off a test without touching your code.Instead of waiting for CI or redeploys, Avido sends an HTTP
POST to an endpoint that you control.
| Benefit | What it unlocks |
|---|---|
| Continuous coverage | Run tests on prod/staging as often as you like and automated. |
| SME‑friendly | Non‑developers trigger & tweak tasks from the Avido UI. |
How it works
- A test is triggered in the dashboard or automatically.
- Avido POSTs to your configured endpoint.
- Validate the
signature+timestampwith our API/SDK. - Run your LLM flow using
promptfrom the payload. - Emit a trace that includes
testIdto connect results in Avido. - Return
200 OK– any other status tells Avido the test failed.
Validating a webhook with the API requires both
x-api-key and x-application-id
headers. Use the application ID that issued the API key.Payload example
When Avido triggers your webhook endpoint, it sends:Webhook payload
| Header | Purpose |
|---|---|
x-avido-signature | HMAC signature of the payload |
x-avido-timestamp | Unix ms timestamp (in milliseconds) the request was signed |
testIdis optional and only included when running actual testsmetadatais optional and only included when available from the originating task
Verification flow
If validation fails, respond 401 (or other 4xx/5xx). Avido marks the test as failed.Code examples
Next steps
- Send us Trace events.
- Schedule or manually tasks from Tasks in the dashboard.
- Invite teammates so they can craft evals and eyeball results directly in Avido.