Authorization header. Every successful response includes an X-Credits-Remaining header so you can track credit usage in real time.
Base URL
Request Shape
Every endpoint in the API usesPOST and follows the same envelope: a JSON body with an action field that selects the operation, and (for most actions) a data object with parameters. This keeps a single URL per resource while exposing multiple operations.
Resources
The API is organized around five resources, grouped into Tests and Admin:| Resource | Description |
|---|---|
| Health | Manage and run HTTP health checks against your routes |
| Visual | Manage and run visual regression tests across devices |
| Flow | List, run, inspect, delete, or schedule recorded browser flows |
| Transactions | List transactions belonging to the authenticated user |
| Notifications | List, add, or delete in-app notifications |
Credits
Actions that trigger work (running a health check, running a visual test, replaying a flow, scheduling any of the above) consume credits. Every successful response returns:402 Payment Required.
Error Handling
When a request fails, the API returns a consistent JSON error object withsuccess: false and machine-readable fields:
| HTTP Status | Meaning |
|---|---|
400 | The request payload is invalid — check the schema for the action you sent |
401 | The API key is missing, invalid, disabled, or expired |
402 | Your available credits have been exhausted |
403 | Your key is valid but lacks permission, or the target domain is unverified |
404 | The referenced resource (route, flow, notification) was not found |
409 | Resource is already scheduled or running |
429 | API key rate limit exceeded — back off and retry |
500 | Unexpected server error — contact support if it persists |
503 | (Flow only) Replay could not be queued |
Next Steps
Authentication
Generate an API key and authenticate your requests.
Flow
List, run, and schedule recorded flows via the API.