Skip to main content
GET
Get a monitor with profiles and recent events
Job-change monitoring requires a V2 workspace API key. V1 (Bubble) API keys are not supported by these endpoints. Monitors and monitoring credits belong to the V2 workspace associated with the key.
Retrieve one monitor by monitor_id. The response contains all profiles, including soft-removed profiles, and up to the latest 200 events ordered newest first.
Use the profile status and removed_at fields to distinguish an active profile from one removed from future checks. Profile status is pending, baseline, checked, unavailable, failed, or removed. Historical events remain available after a profile is removed.
The monitor object reports next_check_at and last_successful_check_at as ISO 8601 timestamps. A paused monitor has no next check scheduled. When a check could not start or stopped early, run_block_reason (for example insufficient_credits) and run_block_detail explain why; they clear when a later check starts. results_table_id, results_status and results_error describe the results table that receives one row per new event. A monitor can contain up to 10,000 active profiles under the same schedule and webhook. Checks run asynchronously and large checks can take time. Internally, profiles are processed in batches with durable progress, so a retried check keeps its billing identity and does not charge a profile twice. Profiles added after a check starts join the next check. A profile’s first successful check establishes its baseline without emitting a job-change event.

Next step

Use List job-change events when you need cursor pagination beyond the latest 200 events or webhook delivery receipts.

Authorizations

Authorization
string
header
required

Use an Airscale workspace API key. Never expose the key in client-side code.

Path Parameters

monitor_id
string<uuid>
required

Response

The monitor detail.

monitor
object
required
profiles
object[]
required
events
object[]
required