Multi-step checks

A multi-step check runs several requests in order and stops at the first failure. It is the closest thing to a customer using your product.

A sign-in example

step 1: POST /v1/session
  body: { email, password }
  save: token = json.token
step 2: GET /v1/me
  header: Authorization: Bearer $token
  expect: status = 200

step 1: POST /v1/session
  body: { email, password }
  save: token = json.token
step 2: GET /v1/me
  header: Authorization: Bearer $token
  expect: status = 200

step 1: POST /v1/session
  body: { email, password }
  save: token = json.token
step 2: GET /v1/me
  header: Authorization: Bearer $token
  expect: status = 200

Saving values

Use save to keep a value from a response. Use it later as $name in URLs, headers and bodies.

Limits

• 10 steps per monitor

• 60 seconds in total

• Values are not stored after the check ends