At a glance
- Availability: Experimental (how to enable).
- Auth: API key.
- Connection: The key comes from
BETTERSTACK_API_TOKEN. - Docs: https://betterstack.com/docs/uptime/api/getting-started-with-uptime-api/
Credentials
Set these per environment. See Connect an integration.| Variable | Required | Description |
|---|---|---|
BETTERSTACK_API_TOKEN | Yes | Better Stack Uptime API token (global token or team-scoped Uptime token) Docs. |
Setup
- Sign up for Better Stack: Create a free account at https://betterstack.com and add at least one uptime monitor or heartbeat so the API returns data.
- Create an API token: In Better Stack go to API tokens. Use a global API token, or create a team-scoped token in the ‘Uptime API tokens’ section.
- Set the environment variable: Add the token to your .env as BETTERSTACK_API_TOKEN=…
- Verify access: Run List Monitors.
- This connector covers the Uptime API (uptime.betterstack.com) only - the Telemetry/Logs API uses a different token and host and is not included
- Responses follow JSON:API: items are under data[] with attributes, pagination links under pagination
- Incidents use the newer /api/v3 path; monitors and heartbeats use /api/v2
Tools
| Tool | Access | Description |
|---|---|---|
| List Monitors | Read | List uptime monitors, optionally filtered by URL or name |
| Get Monitor | Read | Get a monitor’s configuration and current status |
| Get Monitor Availability | Read | Get a monitor’s availability (SLA) summary for a time range |
| List Incidents | Read | List incidents, optionally limited to a date range or unresolved only |
| List Heartbeats | Read | List heartbeat (cron/job) monitors and their status |
Example prompts
- List my Better Stack monitors and flag any that are not in the ‘up’ status, plus any unresolved incidents.
- Get the availability summary for my main Better Stack monitor over the last 30 days.