POST
/
v1
/
triggers
/
checks
/
{checkId}
Create the check trigger
curl --request POST \
  --url https://api.checklyhq.com/v1/triggers/checks/{checkId} \
  --header 'Authorization: <api-key>'
{
  "id": 1,
  "token": "h7QMmh8c0hYw",
  "created_at": "2023-12-25",
  "called_at": "2023-12-25",
  "updated_at": "2023-12-25",
  "checkId": "a13a7875-ec45-4780-b39f-675ec288cfe1"
}

​
Overview

The Trigger Check Execution endpoint allows you to manually execute a specific check outside of its scheduled runs. This is useful for on-demand testing, debugging, and immediate validation. Common Use Cases:
  • Manual Testing
  • Deployment Validation
  • Debugging Issues
  • Immediate Health Checks
Manually triggered checks execute immediately and results are recorded alongside scheduled runs. Triggered executions count toward your account’s check execution limits.

Authorizations

​
Authorization
string
header
required

The Checkly Public API uses API keys to authenticate requests. You can get the API Key here.

Your API key is like a password: keep it secure!

Authentication to the API is performed using the Bearer auth method in the Authorization header and using the account ID.

For example, set Authorization header while using cURL:

curl -H "Authorization: Bearer [apiKey]" "X-Checkly-Account: [accountId]"

Headers

​
x-checkly-account
string

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

Path Parameters

​
checkId
string
required

Response

Created

​
id
number
required
Example:

1

​
token
string
required
Example:

"h7QMmh8c0hYw"

​
created_at
string<date>
required
​
checkId
string
required
Example:

"a13a7875-ec45-4780-b39f-675ec288cfe1"

​
called_at
string<date>
​
updated_at
string<date>