POST /api/v1/synthetics/tests with type 'api' and subtype 'multi' to create a multistep test; each step in config.steps has its own request, assertions, and extractedValues
In the first step, add an extractedValue with type 'http_body' and a jsonPath parser to capture the access token from a login response
Reference the extracted variable in subsequent steps using {{ extracted_variable_name }} syntax in headers or body
Set assertions on each step independently, e.g., statusCode equals 200, responseTime lessThan 2000
Assign the test to one or more locations and configure a schedule frequency (minimum 1 minute for API tests)
Attach a monitor to the test via config.monitor.notification_preset_name or configure alerting rules on the underlying synthetic monitor
Known gotchas
Extracted variables are scoped to the test run and cannot be shared across separate test definitions
If an early step fails its assertions, subsequent steps are skipped and the test is marked failed — design login steps to be highly reliable
Rate limits on the Datadog Synthetics API: check current limits in the API reference before bulk-creating tests in CI pipelines
Give your agent this knowledge — and 200+ more routes
One MCP install gives any agent live access to the full route map, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp