Accounts11

Alert channels6

Alert notifications1

Analytics12

Badges2

Check alerts2

Check groups11

Check results4

Check sessions7

Check status2

Checks16

Client certificates4

Dashboards5

Deployment Triggers2

Environment variables5

Error Groups4

Heartbeats5

Incident Updates3

Incidents4

Location1

Maintenance windows12

Monitors7

Private locations8

Reporting1

Rocky AI3

Runtimes2

Snippets5

Static IPs6

Status Page Incidents10

Status Page Services5

Status Pages8

Test Session Error Groups4

Test sessions7

Triggers6

Analytics

Multistep checks

Fetch detailed availability metrics and aggregated or non-aggregated Multistep Check metrics across custom time ranges. Rate-limiting is applied to this endpoint, you can send 30 requests / 60 seconds at most.

get/v1/analytics/multistep-checks/{id}

Path parameters

idstring uuid required

Query parameters

fromstring date

Custom start time of reporting window in unix timestamp format. Setting a custom "from" timestamp overrides the use of any "quickRange".

tostring date

Custom end time of reporting window in unix timestamp format. Setting a custom "to" timestamp overrides the use of any "quickRange".

Preset reporting windows are used for quickly generating report on commonly used windows. Can be overridden by using a custom "to" and "from" timestamp.

aggregationIntervalnumber

The time interval to use for aggregating metrics in minutes. For example, five minutes is 5, 24 hours is 1440.

Example:1440

The time interval to use for aggregating metrics in minutes. For example, five minutes is 5, 24 hours is 1440.

filterByStatusstring[]

Filter based on whether a check result was either failing or passing

[
  "failure"
]

groupBy'runLocation'

Determines how the series data is grouped. Note that grouped queries are a bit more expensive and might take longer.

metricsstring[] required

Available metrics for Multistep Checks. You can pass multiple metrics as a comma separated string.

limitinteger

Limit the number of results

pagenumber

Page number

Headers

x-checkly-accountstring uuid

Your Checkly account ID, you can find it at https://app.checklyhq.com/settings/account/general

Response

Success

checkIdstring uuid

namestring

activatedboolean

mutedboolean

frequencynumber

fromstring date-time

tostring date-time

tagsstring[]

Changes

Changed in 1 of the 4 revisions of this API.6412

Aug 12, 202687d29dc7b4fe6412See the full diff
- ▲
  for the path request parameter id, the minLength was increased from 0 to 1
  request-parameter-min-length-increased
- ▲
  for the header request parameter x-checkly-account, the type/format was changed from string/ to string/uuid
  request-parameter-type-changed
- ▲
  for the path request parameter id, the type/format was changed from string/ to string/uuid
  request-parameter-type-changed
- ▲
  the from response's property type/format changed from string/date to string/date-time for status 200
  response-property-type-changed
- ▲
  the series/items/ response's property type/format changed from string/ to object/ for status 200
  response-property-type-changed
- ▲
  the to response's property type/format changed from string/date to string/date-time for status 200
  response-property-type-changed
- ●
  for the query request parameter page, the exclusiveMinimum was set to true
  request-parameter-exclusive-min-set
- ●
  for the query request parameter page, the min was set to 0.00
  request-parameter-min-set
- ●
  removed the optional property attributes from the response with the 401 status
  response-optional-property-removed
- ●
  removed the optional property attributes from the response with the 429 status
  response-optional-property-removed
- ○
  added the non-success response with the status 400
  response-non-success-status-added
- ○
  added the non-success response with the status 404
  response-non-success-status-added
- ○
  the response property message became required for the status 401
  response-property-became-required
- ○
  the response property message became required for the status 403
  response-property-became-required
- ○
  the response property message became required for the status 429
  response-property-became-required
- ○
  removed the 401.00 enum value from the statusCode response property for the response status 401
  response-property-enum-value-removed
- ○
  removed the 403.00 enum value from the statusCode response property for the response status 403
  response-property-enum-value-removed
- ○
  removed the 429.00 enum value from the statusCode response property for the response status 429
  response-property-enum-value-removed
- ○
  removed the Forbidden enum value from the error response property for the response status 403
  response-property-enum-value-removed
- ○
  removed the Too Many Requests enum value from the error response property for the response status 429
  response-property-enum-value-removed
- ○
  removed the Unauthorized enum value from the error response property for the response status 401
  response-property-enum-value-removed
- ○
  added the required property series/items/data to the response with the 200 status
  response-required-property-added
This revision also has 566 changes that name no endpoint, such as unreferenced schemas being removed. See the revision's changelog

Full history