Guides
Task-oriented instructions for setting up APIContext, building monitors, and acting on what they find. New to APIContext? Start with Monitor your first API.
The guides are grouped by task. Each group starts with the page most people need first.
| Group | Use it to | Start with |
|---|---|---|
| Projects, team, and access | Set up projects and organizations, invite people, and copy or move resources | Projects |
| Create monitors | Add API, browser, MCP, and Postman monitors, or import them from a spec | Add an API monitor |
| Authentication | Give monitors the credentials, tokens, and certificates an API needs | Monitor Authentication |
| Workflows, variables, and assertions | Chain calls, pass values between them, and decide what counts as a pass | Workflows |
| Schedule and run monitors | Run monitors on a schedule or on demand, pause them for maintenance, and add private nodes | Managing Schedules |
| Results and analytics | Read results, dashboards, reports, and the CASC score | Understanding the Results |
| Alerts and notifications | Get told when a monitor fails, by email, webhook, Slack, Teams, or PagerDuty | Setting Alerts |
| Conformance and SLOs | Check APIs against standards and specs, and track service-level objectives | Conformance |
| Integrations and data export | Send results to observability tools and bring in third-party data | Org-level Integrations |
| API and CLI | Automate APIContext from scripts, pipelines, and agents | Install and set up the CLI |
| Help and support | Find answers, contact support, and follow platform status | FAQs |
For what a monitor, workflow, or result is, see Concepts. For every endpoint and field, see the API reference and the CLI reference.