Acknowledge Incident
Tool to acknowledge an ongoing incident. Use when you need to mark an incident as being worked on, which prevents further escalations. Acknowledging an incident signals that someone is actively addressing the issue.
Better Stack provides monitoring, logging, and incident management solutions to help teams ensure the reliability and performance of their applications.
Tool to acknowledge an ongoing incident. Use when you need to mark an incident as being worked on, which prevents further escalations. Acknowledging an incident signals that someone is actively addressing the issue.
# Batch create catalog records Allows creation of multiple Catalog records at once. POST /api/v2/catalog/relations/{relation_id}/records/batch Requires a Better Stack Incidents API token with access to the resource.
# Batch remove catalog records Permanently deletes **all** existing Catalog records for a given relation. DELETE /api/v2/catalog/relations/{relation_id}/records/batch Requires a Better Stack Incidents API token with access to the resource.
# Batch update catalog records Allows replacing **all** Catalog records for a given relation at once. This is a destructive operation and will remove all existing records for the relation before creating new ones. PUT /api/v2/catalog/relations/{relation_id}/records/batch Requires a Better Stack Incidents API token with access to the resource.
Create or partially update Catalog records in one atomic batch. Matches existing records by primary attribute values, regardless of value order; an empty primary attribute matches only an empty one. Matching records update only supplied attributes: omitted attributes retain their values, and an empty values array clears an attribute. Nonmatching inputs create records; existing records not matched by the batch remain unchanged. If any record cannot be saved, none are saved, including ambiguous matches or duplicate primary values within the batch. Returns records in input order and created/updated IDs. Requires a Better Stack Incidents API token with access to the relation.
# Bulk update on-call schedule events Replace all current and future on-call events in a single on-call schedule: - Delete all events that start today at 0:00 UTC or later. - Create new events. All newly created events also must start today at 0:00 UTC or later. PUT /api/v2/on-calls/{schedule_id}/events Requires a Better Stack Incidents API token with access to the resource.
# Create Amazon SNS integration Returns either a newly created Amazon SNS integration, or validation errors. Subscribe a topic to the returned `url` to start receiving notifications, as described in the [Amazon SNS integration guide](https://betterstack.com/docs/uptime/integrations/integrating-with-better-uptime/amazon-sns/). Leave **Enable raw message delivery** off on that subscription, or every notification is rejected with `400`. POST /api/v2/amazon-sns Requires a Better Stack Incidents API token with access to the resource.
# Create AWS CloudWatch integration Returns either a newly created AWS CloudWatch integration, or validation errors. POST /api/v2/aws-cloudwatch-integrations Requires a Better Stack Incidents API token with access to the resource.
Create an override to subscribe or unsubscribe one CloudWatch log group. Requires an `aws` source with an AWS account already connected and a Telemetry API token with access to the source. Set subscribed to true to ingest the log group or false to skip it, overriding the source's automatic subscription setting. An override can be created before discovery of the log group; creating a duplicate region/name override returns HTTP 422.
# Create Azure integration Returns either a newly created Azure integration, or validation errors. POST /api/v2/azure-integrations Requires a Better Stack Incidents API token with access to the resource.
# Create catalog attribute Returns either a newly created Catalog attribute, or validation errors. POST /api/v2/catalog/relations/{relation_id}/attributes Requires a Better Stack Incidents API token with access to the resource.
# Create catalog record Returns either a newly created Catalog record, or validation errors. POST /api/v2/catalog/relations/{relation_id}/records Requires a Better Stack Incidents API token with access to the resource.
# Create catalog relation Returns either a newly created Catalog relation, or validation errors. POST /api/v2/catalog/relations Requires a Better Stack Incidents API token with access to the resource.
Create a chart on a specific dashboard. Requires a Telemetry API token. Only line_chart supports multiple queries. funnel_chart cannot be created through the API. For SQL queries, filter dt with {{start_time}} and {{end_time}}; {{time}} only groups timestamps into buckets. Overlapping positions cause automatic layout consolidation; the response may include warnings.
# Create a chart comment Pins a comment to a point in time on a chart, the same comment you get by clicking the chart in the Better Stack interface. Use it to mark releases, deployments, and incidents on your charts from your own scripts. POST /api/v2/dashboards/{dashboard_id}/charts/{chart_id}/comments Requires a Telemetry API token with access to the resource.
# Create a collector Creates a new Better Stack collector. [info] The `platform` and `data_region` attributes can only be set during creation and cannot be updated later. A custom bucket can only be added during creation; its key pair can be rotated with [Update collector](https://betterstack.com/docs/logs/api/update-a-collector/). [/info] POST /api/v1/collectors Requires a Telemetry API token with access to the resource.
# Create a collector metric target Creates a new monitoring target on a collector. [info] Each target kind accepts a specific set of connection fields. Sending a field that does not apply to the chosen kind (for example, `ssl_mode` on a `redis` target) will return a validation error. [/info] POST /api/v1/collectors/{collector_id}/targets Requires a Telemetry API token with access to the resource.
Create a ClickHouse connection using a global API token, not a team token. The password is returned only in this creation response and cannot be retrieved later. Connections are organization-wide; optionally scope data access with either team_names or team_ids, not both. Omit data_region to create the connection in all regions; private cluster names are also accepted.
# Create a dashboard Creates a new dashboard, including its variables and other properties. POST /api/v2/dashboards Requires a Telemetry API token with access to the resource.
# Create a dashboard alert Creates a new alert for a specific dashboard chart. POST /api/v2/dashboards/{dashboard_id}/charts/{chart_id}/alerts Requires a Telemetry API token with access to the resource.
# Create a dashboard group Creates a new dashboard group for organizing dashboards. POST /api/v2/dashboard-groups Requires a Telemetry API token with access to the resource.
# Create a dashboard section Creates a new section on a specific dashboard. POST /api/v2/dashboards/{dashboard_id}/sections Requires a Telemetry API token with access to the resource.
# Create Datadog integration Returns either a newly created Datadog integration, or validation errors. POST /api/v2/datadog-integrations Requires a Better Stack Incidents API token with access to the resource.
# Create Elastic integration Returns either a newly created Elastic integration, or validation errors. POST /api/v2/elastic-integrations Requires a Better Stack Incidents API token with access to the resource.
# Create e-mail integration Returns either a newly created e-mail integration, or validation errors. POST /api/v2/email-integrations Requires a Better Stack Incidents API token with access to the resource.
Creates a new escalation policy for incident management. Escalation policies define who gets notified and in what order when incidents occur. Supports multiple step types: 'escalation' (notify members), 'instructions' (guidance text), 'time_branching' (route by schedule), and 'metadata_branching' (route by incident metadata). For escalation steps, a valid urgency_id from the Severities API is required.
Tool to create a new escalation policy group. Use when you need to organize related escalation policies under a single logical group.
# Create an exploration Creates a new exploration, including its chart, queries, and variables. POST /api/v2/explorations Requires a Telemetry API token with access to the resource.
# Create an exploration alert Creates a new alert for a specific exploration. POST /api/v2/explorations/{exploration_id}/alerts Requires a Telemetry API token with access to the resource.
# Create an exploration group Creates a new exploration group for organizing explorations. POST /api/v2/exploration-groups Requires a Telemetry API token with access to the resource.
# Create Google Monitoring integration Returns either a newly created Google Monitoring integration, or validation errors. POST /api/v2/google-monitoring-integrations Requires a Better Stack Incidents API token with access to the resource.
# Create Grafana integration Returns either a newly created Grafana integration, or validation errors. POST /api/v2/grafana-integrations Requires a Better Stack Incidents API token with access to the resource.
Tool to create a new heartbeat monitor for cron jobs and scheduled tasks. Use when you need to set up monitoring for a service that should send regular heartbeat signals.
Tool to create a new heartbeat group. Use when you need to organize related heartbeat checks under a single, logical group. Example prompt: "Create a new heartbeat group named 'Backend services'."
Tool to create a new incident and alert the on-call person. Use when you need to manually report an incident or trigger escalation workflows. The incident will be routed according to the specified escalation policy or default team settings.
Tool to create a new comment on an incident. Use when you need to add documentation, updates, or notes to an existing incident in Better Stack.
# Create incoming webhook Returns either a newly created incoming webhook, or validation errors. POST /api/v2/incoming-webhooks Requires a Better Stack Incidents API token with access to the resource.
Tool to create or update a metadata record for a resource. Metadata provides key-value associations for resources like monitors, heartbeats, or incidents. Use when you need to tag or annotate resources with custom data. Existing values for the specified key will be completely replaced.
# Create a metric Returns a newly created metric or label. POST /api/v2/sources/{source_id}/metrics Requires a Telemetry API token with access to the resource.
Tool to create a new uptime monitor for a URL or service. Use when you need to set up monitoring for websites, APIs, servers, or network services. Supports multiple monitor types including HTTP/HTTPS status checks, keyword monitoring, ping, TCP/UDP, email protocols, DNS queries, and browser automation with Playwright.
Tool to create a new monitor group. Use when you need to organize related monitors under a single, logical group for better dashboard organization.
# Create New Relic integration Returns either a newly created New Relic integration, or validation errors. POST /api/v2/new-relic-integrations Requires a Better Stack Incidents API token with access to the resource.
# Create an on-call schedule event Create a new event in the given on-call schedule. POST /api/v2/on-calls/{schedule_id}/events Requires a Better Stack Incidents API token with access to the resource.
Tool to create a new on-call schedule. Use when you need to set up a new on-call calendar for managing team rotations.
# Create outgoing e-mail Returns either a newly created outgoing e-mail integration, or validation errors. See the [outgoing e-mails guide](https://betterstack.com/docs/uptime/integrations/integrating-with-better-uptime/outgoing-emails/) for the dashboard walkthrough. POST /api/v2/outgoing-emails Requires a Better Stack Incidents API token with access to the resource.
Tool to create a new outgoing webhook integration. Use when you need to register an endpoint to receive event notifications from Better Stack.
# Create PagerDuty integration Returns either a newly created PagerDuty integration, or validation errors. POST /api/v2/pager-duty-webhooks Requires a Better Stack Incidents API token with access to the resource.
# Create Prometheus integration Returns either a newly created Prometheus integration, or validation errors. POST /api/v2/prometheus-integrations Requires a Better Stack Incidents API token with access to the resource.
# Create an on-call schedule rotation Creates an on-call rotation. This creates consecutive on-call events for specified users, rotating through them until reaching the end date, and removes any existing non-override events within this range. Without `working_hours`, this only creates events that end after 0:00 UTC today. With `working_hours`, it creates events from now on, only inside the given windows. POST /api/v2/on-calls/{schedule_id}/rotation Requires a Better Stack Incidents API token with access to the resource.
Tool to create a new severity level (urgency) for incident management. Use when you need to define notification preferences for different incident severity levels.
# Create a source Returns a newly created source. POST /api/v2/sources Requires a Telemetry API token with access to the resource.
Tool to create a new source group. Use when you have finalized the group name (and optional sort index) and need to organize related log sources under that group.
# Create a Splunk integration Returns either a newly created Splunk On-Call integration, or validation errors. POST /api/v2/splunk-on-calls Requires a Better Stack Incidents API token with access to the resource.
# Create status page Returns a newly created status page or validation errors. POST /api/v2/status-pages Requires a Better Stack Incidents API token with access to the resource.
Tool to create a new status page group. Use when you need to organize related status pages under a single logical group with a descriptive name.
Tool to create a new status page report (incident or maintenance). Use when you need to publish a status update about an ongoing incident or scheduled maintenance on a status page.
Tool to create a new status page resource. Use when you need to add a monitor, heartbeat, or other resource to a status page for public visibility tracking.
Tool to create a new section on a status page. Use when organizing resources into logical groups (e.g., by datacenter or service type). Leave name blank to hide the section header.
# Create status page subscriber Creates a confirmed e-mail subscriber for a status page. Creating a subscriber who previously unsubscribed subscribes that e-mail again. Creating an e-mail address that is already actively subscribed returns `422`. POST /api/v2/status-pages/{status_page_id}/subscribers Requires a Better Stack Incidents API token with access to the resource.
Tool to create a new status update for an existing status report. Use when you need to post an update about the current state of an incident or maintenance. The update can include a message, affected resources with their status, and optionally notify subscribers.
Tool to create a new urgency group (severity group) for incident categorization. Use when you need to define severity levels for monitoring alerts and incidents.
# Remove an alert Permanently deletes an alert by its ID. DELETE /api/v2/alerts/{id} Requires a Telemetry API token with access to the resource.
Permanently delete an Amazon SNS integration from Better Stack. Stops accepting topic notifications but leaves the AWS SNS subscription intact; remove that subscription separately in AWS. Returns no content on success. Requires a Better Stack Incidents API token with access to the resource.
# Remove AWS CloudWatch integration Permanently deletes an existing AWS CloudWatch integration. DELETE /api/v2/aws-cloudwatch-integrations/{aws_cloudwatch_integration_id} Requires a Better Stack Incidents API token with access to the resource.
Delete a log group subscription override and restore automatic behavior. The log group follows the source's auto-subscribe setting afterward; deleting an override does not necessarily unsubscribe the log group. Requires an aws source with a connected AWS account and a Telemetry API token with access to the resource. Returns an empty response on success (HTTP 204).
# Remove Azure integration Permanently deletes an existing Azure integration. DELETE /api/v2/azure-integrations/{azure_integration_id} Requires a Better Stack Incidents API token with access to the resource.
# Remove catalog attribute Permanently deletes an existing Catalog attribute. DELETE /api/v2/catalog/relations/{relation_id}/attributes/{attribute_id} Requires a Better Stack Incidents API token with access to the resource.
# Remove catalog record Permanently deletes an existing Catalog record. DELETE /api/v2/catalog/relations/{relation_id}/records/{record_id} Requires a Better Stack Incidents API token with access to the resource.
# Remove catalog relation Permanently deletes an existing Catalog relation. DELETE /api/v2/catalog/relations/{relation_id} Requires a Better Stack Incidents API token with access to the resource.
# Remove a chart Permanently deletes a chart from a dashboard. DELETE /api/v2/dashboards/{dashboard_id}/charts/{id} Requires a Telemetry API token with access to the resource.
Permanently remove a chart comment. Success returns no content. Requires a Telemetry API token with access to the resource. Team API tokens can remove only comments with api_authored=true. With an OAuth token, the member's own comments can also be removed. Other members' comments and incident comments synced from Incidents return 403.
# Remove a collector Permanently deletes a collector. This action is irreversible and will also remove all associated configurations and stop data collection. The underlying sources and their data will be deleted asynchronously. DELETE /api/v1/collectors/{id} Requires a Telemetry API token with access to the resource.
# Remove a collector metric target Permanently removes a collector target. The collector will stop monitoring this target on its next configuration sync. DELETE /api/v1/collectors/{collector_id}/targets/{target_id} Requires a Telemetry API token with access to the resource.
Delete an existing ClickHouse connection by its ID. Requires a global API token; team-specific tokens are not supported. Returns no content on success, or 404 when the connection does not exist.
# Remove a dashboard Permanently deletes an existing dashboard. DELETE /api/v2/dashboards/{id} Requires a Telemetry API token with access to the resource.
# Remove a dashboard alert Permanently deletes an alert from a dashboard chart. DELETE /api/v2/dashboards/{dashboard_id}/charts/{chart_id}/alerts/{id} Requires a Telemetry API token with access to the resource.
# Remove a dashboard group Permanently deletes a dashboard group by its ID. [info] Deleting a group does not delete the dashboards within it. Those dashboards will become ungrouped. [/info] DELETE /api/v2/dashboard-groups/{id} Requires a Telemetry API token with access to the resource.
# Remove a dashboard section Permanently deletes a section from a dashboard. DELETE /api/v2/dashboards/{dashboard_id}/sections/{id} Requires a Telemetry API token with access to the resource.
# Remove Datadog integration Permanently deletes an existing Datadog integration. DELETE /api/v2/datadog-integrations/{datadog_integration_id} Requires a Better Stack Incidents API token with access to the resource.
# Remove Elastic integration Permanently deletes an existing Elastic integration. DELETE /api/v2/elastic-integrations/{elastic_integration_id} Requires a Better Stack Incidents API token with access to the resource.
# Remove e-mail integration Permanently deletes an existing e-mail integration. DELETE /api/v2/email-integrations/{email_integration_id} Requires a Better Stack Incidents API token with access to the resource.
Tool to delete an escalation policy by ID. Use when you need to permanently remove an existing escalation policy after confirming its ID.
Tool to delete an escalation policy group by ID. Use when you need to permanently remove an existing escalation policy group after confirming its ID.
# Remove an exploration Permanently deletes an exploration by its ID. [warning] Deleting an exploration also permanently deletes its associated chart, queries, and any configured alerts. This action cannot be undone. [/warning] DELETE /api/v2/explorations/{id} Requires a Telemetry API token with access to the resource.
# Remove an exploration alert Permanently deletes an alert by its ID. DELETE /api/v2/explorations/{exploration_id}/alerts/{id} Requires a Telemetry API token with access to the resource.
# Remove an exploration group Permanently deletes an exploration group by its ID. [info] Deleting a group does not delete the explorations within it. Those explorations will become ungrouped. [/info] DELETE /api/v2/exploration-groups/{id} Requires a Telemetry API token with access to the resource.
# Remove Google Monitoring integration Permanently deletes an existing Google Monitoring integration. DELETE /api/v2/google-monitoring-integrations/{google_monitoring_integration_id} Requires a Better Stack Incidents API token with access to the resource.
# Remove Grafana integration Permanently deletes an existing Grafana integration. DELETE /api/v2/grafana-integrations/{grafana_integration_id} Requires a Better Stack Incidents API token with access to the resource.
Tool to permanently delete a heartbeat by ID. Use when you need to remove a heartbeat that is no longer needed.
Tool to permanently delete a heartbeat group by ID. Use when you need to remove a heartbeat group that is no longer needed.
Tool to permanently delete an existing incident by ID. Use when you need to remove an incident from Better Stack Uptime.
Tool to delete an existing comment from an incident. Use when you need to remove a comment that was previously added via the API. Note: Only comments created via the API can be deleted; comments created in the UI cannot be deleted via the API.
# Remove incoming webhook Permanently deletes an existing incoming webhook. DELETE /api/v2/incoming-webhooks/{incoming_webhook_id} Requires a Better Stack Incidents API token with access to the resource.
# Remove a metric Permanently deletes an existing metric or label. DELETE /api/v2/sources/{source_id}/metrics/{id} Requires a Telemetry API token with access to the resource.
Tool to permanently delete a monitor by ID from Better Stack Uptime. Use when you need to remove a monitor that is no longer needed.
Tool to permanently delete a monitor group by ID from Better Stack Uptime. Use when you need to remove a monitor group that is no longer needed.
# Remove New Relic integration Permanently deletes an existing New Relic integration. DELETE /api/v2/new-relic-integrations/{new_relic_integration_id} Requires a Better Stack Incidents API token with access to the resource.
# Remove on-call schedule event Delete a single event from an on-call schedule. Events starting sooner than today at 0:00 UTC can't be deleted. DELETE /api/v2/on-calls/{schedule_id}/events/{event_id} Requires a Better Stack Incidents API token with access to the resource.
Tool to permanently delete an on-call schedule by ID. Use when you need to remove an on-call calendar that is no longer needed.
# Remove outgoing e-mail Permanently deletes an outgoing e-mail integration. Returns an empty body with status `204 No Content` on success. DELETE /api/v2/outgoing-emails/{integration_id} Requires a Better Stack Incidents API token with access to the resource.
Tool to delete an outgoing webhook integration by ID. Use when you need to permanently remove an existing webhook integration.
# Remove PagerDuty integration Permanently deletes an existing PagerDuty integration. DELETE /api/v2/pager-duty-webhooks/{pager_duty_webhook_id} Requires a Better Stack Incidents API token with access to the resource.
# Remove Prometheus integration Permanently deletes an existing Prometheus integration. DELETE /api/v2/prometheus-integrations/{prometheus_integration_id} Requires a Better Stack Incidents API token with access to the resource.
# Remove an on-call schedule rotation Remove an on-call rotation for a single schedule. This also removes all on-call events generated for this on-call rotation that end after 0:00 UTC today. DELETE /api/v2/on-calls/{schedule_id}/rotation Requires a Better Stack Incidents API token with access to the resource.
Tool to delete a severity (urgency) by ID. Use when you need to permanently remove an existing severity level after confirming its ID.
# Remove a source Permanently deletes an existing source. DELETE /api/v2/sources/{source_id} Requires a Telemetry API token with access to the resource.
Tool to permanently delete a source group by ID from Better Stack Telemetry (Logs). Source groups are used to organize related log sources. Use this action when you need to remove a source group that is no longer needed. Note: This action requires a Telemetry API token (not an Uptime API token). Deleting a source group does not delete the sources within it - they will become ungrouped.
# Remove Splunk integration Permanently deletes an existing Splunk On-Call integration. DELETE /api/v2/splunk-on-calls/{splunk_on_call_id} Requires a Better Stack Incidents API token with access to the resource.
# Remove status page Permanently deletes an existing status page. DELETE /api/v2/status-pages/{status_page_id} Requires a Better Stack Incidents API token with access to the resource.
Tool to delete a status page group by ID. Use when you need to permanently remove an existing status page group.
Tool to permanently delete a status page report by ID from Better Stack Uptime. Use this action when you need to remove an existing status page report that is no longer needed. The report will be permanently deleted and cannot be recovered.
Tool to delete an existing resource from a status page. Use when you need to permanently remove a resource (monitor or heartbeat) that is displayed on a status page.
Tool to permanently delete a status page section by ID. Use when you need to remove a section from a status page that is no longer needed. Sections organize resources on status pages for better visibility.
Remove an e-mail subscriber from a status page by subscriber ID. Creates an unsubscribe record for that e-mail address. Requires a Better Stack Incidents API token with access to the status page.
Remove a status page subscriber by exact email address. Creates an unsubscribe record for that email address. Returns no content on success. Requires a Better Stack Incidents API token with access to the status page.
Tool to delete an existing status update from a status report. Use when you need to permanently remove a status update after confirming its ID.
Remove a team member or cancel a pending invitation by e-mail. This action cannot be undone. Admins cannot be removed through the API. Removing a billing_admin requires a global API token because that role applies to every team. With a global token, provide team_name to select the team. Sends email and optional team_name as query parameters to the Better Stack organization API.
# Remove a team member from team by ID Removes a member from the team by their ID. This action cannot be undone. [info] Removing a user with the `admin` role is not permitted via the API. Removing a user with the `billing_admin` role requires a global API token, because Billing admin applies to every team in your organization. [/info] DELETE /api/v2/team-members/{id} Requires a Better Stack Incidents API token with access to the resource.
Tool to permanently delete an urgency group (severity group) by ID. Use when you need to remove an existing severity group that is no longer needed.
Tool to escalate an ongoing incident to a user, team, schedule, policy, or organization. Use when you need to route an active incident to the appropriate responders with specified notification channels (call, SMS, email, push).
# Export a dashboard Retrieves the full configuration of a dashboard or a public template as a JSON object. This is useful for backing up dashboards or creating new dashboards via the [import endpoint](https://betterstack.com/docs/logs/api/dashboards/import/). This endpoint can be used to export both your [own dashboards](https://betterstack.com/docs/logs/api/dashboards/list/) and [dashboard templates](https://betterstack.com/docs/logs/api/dashboards/templates/). GET /api/v2/dashboards/{id}/export Requires a Telemetry API token with access to the resource.
# Get a single alert Retrieves a single alert by its ID from any context (dashboard or exploration). GET /api/v2/alerts/{id} Requires a Telemetry API token with access to the resource.
# Get Amazon SNS integration Returns a single Amazon SNS integration by ID. GET /api/v2/amazon-sns/{amazon_sns_integration_id} Requires a Better Stack Incidents API token with access to the resource.
# Get AWS CloudWatch integration Returns a single AWS CloudWatch integration by ID. GET /api/v2/aws-cloudwatch-integrations/{aws_cloudwatch_integration_id} Requires a Better Stack Incidents API token with access to the resource.
Get one AWS log group subscription override, including its region, log group name and subscribed state. Requires an aws source with a connected AWS account and a Telemetry API token with access to that source.
# Get Azure integration Returns a single Azure integration by ID. GET /api/v2/azure-integrations/{azure_integration_id} Requires a Better Stack Incidents API token with access to the resource.
# Get catalog attribute Returns a single Catalog attribute by ID. GET /api/v2/catalog/relations/{relation_id}/attributes/{attribute_id} Requires a Better Stack Incidents API token with access to the resource.
# Get a single Catalog record Returns a single Catalog record by ID. GET /api/v2/catalog/relations/{relation_id}/records/{record_id} Requires a Better Stack Incidents API token with access to the resource.
# Get catalog relation Returns a single Catalog relation by ID. GET /api/v2/catalog/relations/{relation_id} Requires a Better Stack Incidents API token with access to the resource.
# Get a single chart Retrieves a single chart by its ID from a specific dashboard. GET /api/v2/dashboards/{dashboard_id}/charts/{id} Requires a Telemetry API token with access to the resource.
# Get a single chart comment Returns a single comment from a chart. GET /api/v2/dashboards/{dashboard_id}/charts/{chart_id}/comments/{id} Requires a Telemetry API token with access to the resource.
# Get a single collector Retrieves details for a single collector by its ID. GET /api/v1/collectors/{id} Requires a Telemetry API token with access to the resource.
# Get a single collector metrics target Returns a single collector target by ID. GET /api/v1/collectors/{collector_id}/targets/{target_id} Requires a Telemetry API token with access to the resource.
Retrieve details of a specific ClickHouse connection by ID. Requires a global API token. Returns connection settings and queryable sources; the password is returned only when creating a connection, not by this action.
# Get a single dashboard Retrieves detailed information for a single dashboard by its ID, including its charts, sections, and variables. GET /api/v2/dashboards/{id} Requires a Telemetry API token with access to the resource.
# Get a single dashboard alert Retrieves a single alert by its ID, scoped to a specific dashboard chart. GET /api/v2/dashboards/{dashboard_id}/charts/{chart_id}/alerts/{id} Requires a Telemetry API token with access to the resource.
# Get a single dashboard group Retrieves a single dashboard group by its ID. GET /api/v2/dashboard-groups/{id} Requires a Telemetry API token with access to the resource.
# Get a single dashboard section Retrieves a single section by its ID from a specific dashboard. GET /api/v2/dashboards/{dashboard_id}/sections/{id} Requires a Telemetry API token with access to the resource.
# Get Datadog integration Returns a single Datadog integration by ID. GET /api/v2/datadog-integrations/{datadog_integration_id} Requires a Better Stack Incidents API token with access to the resource.
# Get Elastic integration Returns a single Elastic integration by ID. GET /api/v2/elastic-integrations/{elastic_integration_id} Requires a Better Stack Incidents API token with access to the resource.
# Get e-mail integration Returns a single e-mail integration by ID. GET /api/v2/email-integrations/:email_integration_id Requires a Better Stack Incidents API token with access to the resource.
Get an escalation policy by ID, including its repeat settings, team information, and selected step details.
Tool to get a single escalation policy group. Use when you need full details of a specific escalation policy group by its ID.
# Get a single exploration Retrieves a single exploration by its ID, including the full chart, query, and variable configurations. GET /api/v2/explorations/{id} Requires a Telemetry API token with access to the resource.
# Get a single exploration alert Retrieves a single alert by its ID, scoped to a specific exploration. GET /api/v2/explorations/{exploration_id}/alerts/{id} Requires a Telemetry API token with access to the resource.
# Get a single exploration group Retrieves a single exploration group by its ID. GET /api/v2/exploration-groups/{id} Requires a Telemetry API token with access to the resource.
# Get Google Monitoring integration Returns a single Google Monitoring integration by ID. GET /api/v2/google-monitoring-integrations/{google_monitoring_integration_id} Requires a Better Stack Incidents API token with access to the resource.
# Get Grafana integration Returns a single Grafana integration by ID. GET /api/v2/grafana-integrations/{grafana_integration_id} Requires a Better Stack Incidents API token with access to the resource.
Tool to get a single heartbeat by ID. Use when you need to fetch details of a specific heartbeat.
Tool to retrieve availability summary for a specific heartbeat. Use when you need availability metrics for a heartbeat within an optional date range.
Tool to get a single heartbeat group by ID. Use when you need to fetch details of a specific heartbeat group.
Tool to get a single comment from an incident. Use when you need to retrieve details of a specific comment on a Better Stack incident.
# Get incoming webhook Returns a single incoming webhook by ID. GET /api/v2/incoming-webhooks/:incoming_webhook_id Requires a Better Stack Incidents API token with access to the resource.
# Get Jira integration Returns a single Jira integration by ID. GET /api/v2/jira-integrations/:jira_integration_id Requires a Better Stack Incidents API token with access to the resource.
Tool to get a single monitor. Use when you need full details of a specific monitor by its ID.
Get an availability summary for a specific monitor over an optional date range, including uptime percentage, downtime, incident count, and incident duration statistics.
Tool to get a single monitor group by ID. Use when you need to fetch details of a specific monitor group.
Tool to get all monitors belonging to a monitor group. Use when you need to retrieve all monitors within a specific monitor group, with optional pagination support.
Retrieves response time metrics for a specific uptime monitor, including DNS, connection, TLS handshake, and data transfer timings grouped by region. Results are limited to one record per region by default; an optional limit can request more.
# Get New Relic integration Returns a single New Relic integration by ID. GET /api/v2/new-relic-integrations/{new_relic_integration_id} Requires a Better Stack Incidents API token with access to the resource.
# Get a single on-call schedule event Get a single event from an on-call schedule. GET /api/v2/on-calls/{schedule_id}/events/{event_id} Requires a Better Stack Incidents API token with access to the resource.
Tool to get a single on-call schedule by ID. Use when you need to retrieve who is currently on-call for a specific schedule. Optionally specify a date to check on-call status at a specific time.
# Get outgoing e-mail Returns a single outgoing e-mail integration by ID. GET /api/v2/outgoing-emails/{integration_id} Requires a Better Stack Incidents API token with access to the resource.
Tool to get a single outgoing webhook integration by ID. Use when you need to retrieve details of a specific webhook integration.
# Get PagerDuty integration Returns a single PagerDuty integration by ID. GET /api/v2/pager-duty-webhooks/{pager_duty_webhook_id} Requires a Better Stack Incidents API token with access to the resource.
Retrieve organization usage or incurred cost for one product, itemized by resource. Requires a global API token. Discover product IDs and dimension names using the usage overview; dimension=cost returns incurred cost. Defaults to the last 30 days, without pagination, with a maximum requested range of 400 days. Buckets align to calendar days, weeks, months or quarters and may extend beyond the requested range. Non-day buckets use date_from/date_to instead of date. Future end dates are clamped to today.
# Get Prometheus integration Returns a single Prometheus integration by ID. GET /api/v2/prometheus-integrations/{prometheus_integration_id} Requires a Better Stack Incidents API token with access to the resource.
# Get an on-call schedule rotation Returns the currently used on-call rotation for a single on-call schedule. GET /api/v2/on-calls/{schedule_id}/rotation Requires a Better Stack Incidents API token with access to the resource.
Tool to get a single severity level (urgency) by ID. Use when you need to fetch details of a specific urgency configuration.
# Get Slack integration Returns a single Slack integration by ID. GET /api/v2/slack-integrations/{slack_integration_id} Requires a Better Stack Incidents API token with access to the resource.
# Get a single source Get a single source by its ID. GET /api/v2/sources/{source_id} Requires a Telemetry API token with access to the resource.
# Get a single source group Get a single source group by its ID. GET /api/v1/source-groups/{id} Requires a Telemetry API token with access to the resource.
# Get Splunk integration Returns a single Splunk On-Call integration by ID. GET /api/v2/splunk-on-calls/{splunk_on_call_id} Requires a Better Stack Incidents API token with access to the resource.
Tool to get a single status page by ID. Use when you need detailed information about a specific status page.
Tool to get a single status page group by ID. Use when you need to retrieve details of a specific status page group.
Tool to get a single status page report by ID. Use when you need detailed information about a specific status report or incident.
Tool to get a single status page resource by ID. Use when you need detailed information about a specific resource on a status page.
Tool to get a single status page section. Use when you need details of a specific section within a status page by its ID.
# Get status page subscriber Returns a single e-mail subscriber of your status page. GET /api/v2/status-pages/{status_page_id}/subscribers/{subscriber_id} Requires a Better Stack Incidents API token with access to the resource.
Tool to get a single status update by its ID. Use when you need details of a specific status update for a status report on your status page.
# Get a single team member Returns a single team member by their ID. This endpoint does not return pending invitations. You can retrieve a specific member or invitation by providing an `email` query parameter in [List all team members API](https://betterstack.com/docs/uptime/api/team-members/list/). The `role` attribute is the team member's role **in the team your API token is scoped to**. A user with different roles in different teams returns different values depending on which team's token you use. Possible values: `admin`, `billing_admin`, `team_lead`, `responder`, `member`, or `custom`. `custom` is returned when the user has a non-system custom role. GET /api/v2/team-members/{id} Requires a Better Stack Incidents API token with access to the resource.
Tool to retrieve the configured Uptime API token. Use when you need the Uptime API token for subsequent authenticated API calls.
Tool to get a single urgency group (severity group) by ID. Use when you need to fetch details of a specific urgency group.
Get organization-wide product usage and incurred costs for an inclusive date range. Requires a global API token. Returns all products without pagination, including product IDs, dimensions and default dimensions for subsequent per-product usage queries. Defaults to the last 30 days when from/to are omitted.
Create a new dashboard from exported JSON, queuing its import asynchronously. Set name or data.name. The response is a minimal dashboard representation; charts and sections may not yet reflect their final imported configuration. Requires a Telemetry API token; global tokens also require team_name.
Invite a user to your organization or add an existing member to another team. Authenticate with a global API token and team_name, or a team-scoped Incidents API token. Assign role by name or role_id from List roles (including custom roles); both must match if supplied together. Defaults to responder. Admin invitations are forbidden. Billing admin invitations require a global token because the role applies across the organization. Returns an invitation when sent (201), or existing member details if already in the team (200).
List alerts accessible to the user across all dashboards and explorations. Returns one page; use page/per_page and the returned pagination links to continue. Requires a Telemetry API token with access to the resource.
List one page of Amazon SNS integrations, optionally filtered by team. Use page/per_page and returned pagination links to continue. Requires a Better Stack Incidents API token with access to the resource.
Tool to list all AWS CloudWatch integrations. Use when you need to retrieve and inspect all configured AWS CloudWatch on-call integrations.
List one page of Amazon CloudWatch log group subscription overrides for an `aws` source with an AWS account already connected. Overrides specify whether Better Stack ingests each log group and take precedence over the source's auto-subscribe setting. Returns overrides, not every discovered log group. Use page/per_page and returned pagination links to continue. Requires a Telemetry API token with access to the source.
Tool to list all Azure integrations. Use when you need to retrieve and inspect all configured Azure on-call integrations.
# List catalog attributes Returns a list of all Catalog attributes for a [Catalog relation](https://betterstack.com/docs/uptime/api/list-all-catalog-relations/). GET /api/v2/catalog/relations/{relation_id}/attributes Requires a Better Stack Incidents API token with access to the resource.
List one page of Catalog records for a relation. Use page/per_page and returned pagination links to continue. Requires a Better Stack Incidents API token with access to the resource.
Tool to list all catalog relations. Use when you need to retrieve all catalog relations, supports pagination.
List one page of chart comments ordered by pinned time, oldest first. Use page/per_page and returned pagination links to continue. Requires a Telemetry API token with access to the resource.
# List all charts Retrieves a list of all charts on a specific dashboard. GET /api/v2/dashboards/{dashboard_id}/charts Requires a Telemetry API token with access to the resource.
# List hosts where a collector is running Returns a list of hosts where the specified collector is running. GET /api/v1/collectors/{id}/hosts Requires a Telemetry API token with access to the resource.
List one page of metrics targets belonging to a collector. Use page/per_page and returned pagination links to continue. Requires a Telemetry API token with access to the resource.
List one page of collectors accessible by the authenticated user. Use page/per_page and returned pagination links to continue. Requires a Telemetry API token with access to the collectors.
List one page of ClickHouse connections. Use page/per_page and the returned pagination links to continue. Retrieve an individual connection for full details including data sources. Passwords are returned only when creating a connection. Requires a global Telemetry API token; team-specific tokens cannot authenticate this endpoint.
# List all alerts in a dashboard Retrieves all alerts associated with a specific dashboard chart. This endpoint is not paginated. GET /api/v2/dashboards/{dashboard_id}/charts/{chart_id}/alerts Requires a Telemetry API token with access to the resource.
List one page of your team's dashboard groups. Use page/per_page and the returned pagination links to continue. Requires a Telemetry API token with access to the resource.
# List all dashboard sections Retrieves a list of all sections on a specific dashboard. This endpoint is not paginated; it returns all sections for a given dashboard in a single response. GET /api/v2/dashboards/{dashboard_id}/sections Requires a Telemetry API token with access to the resource.
# List dashboard templates Retrieves a list of all available dashboard templates. This endpoint is not paginated and returns all available templates in a single response. [note] The `id` returned for each template can be used with the [Export dashboard](https://betterstack.com/docs/logs/api/dashboards/export/) endpoint to retrieve the full JSON configuration for that template. [/note] GET /api/v2/dashboards/templates Requires a Telemetry API token with access to the resource.
List one page of the team's dashboards, optionally filtered by name or dashboard group. Returns summarized dashboard attributes, not full variables, charts, or sections; retrieve an individual dashboard for its full configuration. Use page/per_page and the returned pagination links to continue. Requires a Telemetry API token.
# List dashboards in a group Retrieves a paginated list of dashboards within a specific group. GET /api/v2/dashboard-groups/{id}/dashboards Returns one page; use page/per_page and the returned pagination links to continue. Requires a Telemetry API token with access to the resource.
Tool to list all Datadog integrations. Use when you need to retrieve and inspect all configured Datadog on-call integrations.
Tool to list Elastic integrations. Use when you need to retrieve and inspect all configured Elastic integrations.
Tool to list email integrations. Use when you need to retrieve and inspect all configured email integrations with optional team filtering and pagination support.
Tool to list all escalation policies. Use when you need to retrieve existing escalation policies with optional filtering by team name.
Tool to list all escalation policy groups. Use when you need to retrieve existing policy groups with optional team filtering and pagination support.
# List all alerts in an exploration Retrieves all alerts associated with a specific exploration. This endpoint is not paginated. GET /api/v2/explorations/{exploration_id}/alerts Requires a Telemetry API token with access to the resource.
List one page of the team's exploration groups. Use page/per_page and returned pagination links to continue. Requires a Telemetry API token with access to the resource.
List one page of your team's exploration summaries. Use page/per_page and the returned pagination links to continue. For full chart, query, and variable configurations, retrieve an individual exploration. Requires a Telemetry API token with access to the resource.
# List explorations in a group Retrieves a paginated list of explorations within a specific group. GET /api/v2/exploration-groups/{id}/explorations Returns one page; use page/per_page and the returned pagination links to continue. Requires a Telemetry API token with access to the resource.
Tool to list all Google Monitoring integrations. Use when you need to view your configured Google Monitoring on-call integrations with pagination support.
Tool to list all Grafana integrations. Use when you need to retrieve and inspect all configured Grafana integrations.
Lists a page of heartbeat groups, with optional team-name filtering and pagination controls.
Lists a page of configured uptime heartbeats, with optional pagination and team-name filtering.
Tool to list all comments on an incident. Use when you need to retrieve all comments associated with a Better Stack incident.
Tool to retrieve all timeline events for an incident. Use when you need to get a chronological history of events, comments, responses, and changes for a specific incident in Better Stack. Returns all timeline items without pagination.
Tool to list all incidents with optional filtering by monitor, heartbeat, date range, or resolution status. Supports pagination with default of 10 per page and maximum of 50.
List one page of incoming webhooks. Use page/per_page and returned pagination links to continue. Requires a Better Stack Incidents API token with access to the resource.
List Jira integrations with optional team filtering and pagination.
List metadata records with optional filtering by team, owner resource ID, or owner resource type, and pagination.
List one page of metrics and labels for a specified source. Use page/per_page and returned pagination links to continue. Requires a Telemetry API token with access to the resource.
Tool to list all monitor groups. Use when you need to retrieve existing monitor groups with optional team filtering and pagination support.
# Lists databases monitored by a collector Returns a list of databases currently being monitored by the specified collector. [info] For security reasons, passwords are never included in the API response. [/info] GET /api/v1/collectors/{id}/databases Requires a Telemetry API token with access to the resource.
Tool to list all monitors. Use when you need to retrieve existing uptime monitors with optional filtering by URL or name and pagination.
Tool to list New Relic integrations. Use when you need to retrieve and inspect all configured New Relic integrations with pagination support.
Tool to list all events for a specific on-call schedule. Use when you need to retrieve the calendar of scheduled on-call periods for a team.
Tool to list all on-call schedules. Use when you need to retrieve all configured on-call calendars.
List one page of outgoing e-mail integrations. Use page/per_page and the returned pagination links to continue. Requires a Better Stack Incidents API token with access to the resource.
Tool to list all outgoing webhook integrations. Use when you need to retrieve configured webhook endpoints for event notifications.
Tool to list PagerDuty integrations. Use when you need to retrieve and inspect all configured PagerDuty integrations.
List configured Prometheus on-call integrations, with optional team filtering and pagination. Each request returns one page of results.
List every organization role in one unpaginated response. Built-in roles (admin, billing_admin, team_lead, responder, member) are returned first, then custom roles. Custom roles share role='custom'; distinguish them by id and name. Pass a role's id as role_id when inviting team members or updating their roles. Requires a Global or Uptime API token; no team_name is needed, including for global tokens spanning multiple teams.
List incident severity levels (urgencies) and their notification settings, optionally filtered by team. Results are paginated.
Tool to retrieve detailed information about a single incident by its ID. Use when you need to get the full details of a specific incident including its status, timeline, affected regions, and notification settings.
List configured Slack channel integrations, with optional team filtering and pagination. Each request returns one page of results.
List one page of your team's source groups. Use page/per_page and returned pagination links to continue. Requires a Telemetry API token with access to the resource.
List one page of your team's existing Telemetry sources. Use page/per_page and the returned pagination links to continue. Includes source configuration and ingestion tokens. Requires a Telemetry API token with access to the sources.
List one page of sources in a source group. Use page/per_page and returned pagination links to continue. Requires a Telemetry API token with access to the resource.
List configured Splunk On-Call integrations, with optional team filtering and pagination. Each request returns one page of results.
Tool to list all status page groups. Use when you need to retrieve existing status page groups with optional pagination.
Tool to list all status updates for a status page report. Use when you need to retrieve updates posted on a specific status page report with optional pagination.
Tool to list all reports on a status page. Use when you need to retrieve existing status page reports with optional pagination via `page` and `per_page`.
Tool to list all resources on a status page. Use when you need to retrieve existing resources with optional pagination.
List sections of a specific status page, with pagination.
# List status page subscribers Returns a list of the existing e-mail subscribers of your status page. GET /api/v2/status-pages/{status_page_id}/subscribers Returns one page; use page/per_page and the returned pagination links to continue. Requires a Better Stack Incidents API token with access to the resource.
Tool to list all your status pages. Use when you need to retrieve existing status pages with optional pagination.
Tool to list status pages within a specific status page group. Use when you need to retrieve all status pages belonging to a particular group with optional pagination.
List one page of team members and pending invitations, or find one by email. Providing email returns a single member or invitation object. Otherwise, use page/per_page and returned pagination links to continue. The role is team-specific: admin, billing_admin, team_lead, responder, member, or custom. A custom-role invitation returns null for role. Requires an Uptime or global API token; global tokens may require team_name to select a team.
Tool to list all urgency groups (severity groups). Use when you need to retrieve existing urgency groups with optional team filtering and pagination support.
Reopen a resolved incident, optionally identifying who reopened it. Requires a Better Stack Incidents API token with access to the incident. Shared incidents cannot be reopened by the receiving team (403). Returns 409 if the incident is not resolved, its monitor has another open incident, or the reopen window has expired.
Tool to resolve an ongoing incident. Use when you need to mark an incident as resolved and close it. Resolving an incident signals that the issue has been fixed and stops any further escalations.
# Update an alert Updates an existing alert by its ID. You only need to provide the fields you want to change. PATCH /api/v2/alerts/{id} Requires a Telemetry API token with access to the resource.
Update an existing Amazon SNS integration, sending only fields to change. Included rule/field collections replace their existing entries entirely; omit them to preserve existing entries. topic_arn and subscription_state are read-only. Requires a Better Stack Incidents API token with access to the resource.
# Update AWS CloudWatch integration Update an existing AWS CloudWatch integration. Send only the parameters you wish to change (eg. `paused`). PATCH /api/v2/aws-cloudwatch-integrations/{aws_cloudwatch_integration_id} Requires a Better Stack Incidents API token with access to the resource.
Subscribe or unsubscribe an existing AWS log group override. Set subscribed to true to ingest the log group or false to skip it. The override takes precedence over automatic subscription. Requires an aws source with a connected AWS account and a Telemetry API token with access to the resource.
# Update Azure integration Update an existing Azure integration. Send only the parameters you wish to change (eg. `paused`). PATCH /api/v2/azure-integrations/{azure_integration_id} Requires a Better Stack Incidents API token with access to the resource.
# Update catalog attribute Update an existing Catalog attribute. PATCH /api/v2/catalog/relations/{relation_id}/attributes/{attribute_id} Requires a Better Stack Incidents API token with access to the resource.
Update a Catalog record, replacing all its attribute values. Attributes omitted from the supplied array become empty. Requires a Better Stack Incidents API token with access to the relation and record.
# Update catalog relation Update an existing Catalog relation. PATCH /api/v2/catalog/relations/{relation_id} Requires a Better Stack Incidents API token with access to the resource.
# Update a chart Updates an existing chart by its ID. You only need to provide the fields you want to change. [info] When updating `queries`, the entire array will be replaced with the one you provide. Partial updates to queries are not supported. [/info] PATCH /api/v2/dashboards/{dashboard_id}/charts/{id} Requires a Telemetry API token with access to the resource.
Update a chart comment's Markdown content or pinned time; send only changed fields. API-authored comments can be updated. With OAuth, the token's team member can also update their own comments. Other comments, including synced incident comments, return 403. user_email is not accepted; change mentions by sending the whole content. Requires a Telemetry API token with access.
# Update a collector Updates an existing collector. Only the provided parameters will be changed. [warning] The `platform` and `data_region` attributes are immutable and cannot be changed after a collector is created. A custom bucket can only be added when creating a collector. [/warning] PATCH /api/v1/collectors/{id} Requires a Telemetry API token with access to the resource.
# Update a collector metrics target Updates an existing collector target. Only include the fields you want to change - omitted fields are preserved. [info] The `kind` field cannot be changed after creation. To switch to a different kind, remove the target and create a new one. [/info] [info] Changing any connection field resets the target's status to `pending` so the collector can re-verify the connection. Connection fields are `host`, `port`, `username`, `password`, `ssl_mode`, `tls`, `scheme`, `listen_ip`, `endpoint`, `api_key`. [/info] PATCH /api/v1/collectors/{collector_id}/targets/{target_id} Requires a Telemetry API token with access to the resource.
# Update a dashboard Updates an existing dashboard by its ID. You only need to provide the fields you want to change. PATCH /api/v2/dashboards/{id} Requires a Telemetry API token with access to the resource.
# Update a dashboard alert Updates an existing alert on a dashboard chart. You only need to provide the fields you want to change. PATCH /api/v2/dashboards/{dashboard_id}/charts/{chart_id}/alerts/{id} Requires a Telemetry API token with access to the resource.
# Update a dashboard group Updates an existing dashboard group by its ID. PATCH /api/v2/dashboard-groups/{id} Requires a Telemetry API token with access to the resource.
# Update a dashboard section Updates an existing section by its ID. You only need to provide the fields you want to change. PATCH /api/v2/dashboards/{dashboard_id}/sections/{id} Requires a Telemetry API token with access to the resource.
# Update Datadog integration Update an existing Datadog integration. Send only the parameters you wish to change (eg. `paused`). PATCH /api/v2/datadog-integrations/{datadog_integration_id} Requires a Better Stack Incidents API token with access to the resource.
# Update Elastic integration Update an existing Elastic integration. Send only the parameters you wish to change (eg. `paused`). PATCH /api/v2/elastic-integrations/{elastic_integration_id} Requires a Better Stack Incidents API token with access to the resource.
Update an existing e-mail integration; send only fields you wish to change. Included rules and field configurations are replaced entirely, deleting previous entries. Send all entries to retain them; omit the attribute to leave it unchanged. Requires a Better Stack Incidents API token with access to the resource.
Tool to update an existing escalation policy. Use when you need to modify policy attributes like name, repeat settings, or escalation steps. Only the fields you provide will be updated (partial updates supported).
Updates an existing escalation policy group's properties. Use to rename a group or change its display order.
# Update an exploration Updates an existing exploration by its ID. You only need to provide the fields you want to change. [info] When updating nested resources like `queries` or `variables`, the entire array will be replaced with the one you provide. [/info] PATCH /api/v2/explorations/{id} Requires a Telemetry API token with access to the resource.
# Update an exploration alert Updates an existing alert by its ID. You only need to provide the fields you want to change. PATCH /api/v2/explorations/{exploration_id}/alerts/{id} Requires a Telemetry API token with access to the resource.
# Update an exploration group Updates an existing exploration group by its ID. PATCH /api/v2/exploration-groups/{id} Requires a Telemetry API token with access to the resource.
# Update Google Monitoring integration Update an existing Google Monitoring integration. Send only the parameters you wish to change (eg. `paused`). PATCH /api/v2/google-monitoring-integrations/{google_monitoring_integration_id} Requires a Better Stack Incidents API token with access to the resource.
# Update Grafana integration Update an existing Grafana integration. Send only the parameters you wish to change (eg. `paused`). PATCH /api/v2/grafana-integrations/{grafana_integration_id} Requires a Better Stack Incidents API token with access to the resource.
Tool to update an existing heartbeat configuration. Use after retrieving a heartbeat and choosing which fields to change.
Updates an existing heartbeat group's properties. Use to rename a group, change its display order, or pause/resume monitoring for all heartbeats in the group.
Tool to update an existing comment on an incident. Use when you need to modify the content of a comment that was previously added to a Better Stack incident.
Update an incoming webhook, sending only the fields to change. Included *_rules and *_fields collections replace their stored entries entirely; omit a collection to preserve its existing entries. Requires a Better Stack Incidents API token with access to the resource.
# Update Jira integration Update an existing Jira integration. Send only the parameters you wish to change (eg. `name`). PATCH /api/v2/jira-integrations/{jira_integration_id} Requires a Better Stack Incidents API token with access to the resource.
# Update a metric Updates an existing metric or label. At least one of `name`, `sql_expression`, or `aggregations` must be provided. PATCH /api/v2/sources/{source_id}/metrics/{id} Requires a Telemetry API token with access to the resource.
Tool to update an existing uptime monitor configuration. Use when you need to modify settings of an existing monitor such as check frequency, notification preferences, URLs, or monitoring behavior.
Updates an existing monitor group's properties. Use to rename a group, change its display order, or pause/resume monitoring for all monitors in the group.
# Update New Relic integration Update an existing New Relic integration. Send only the parameters you wish to change (eg. `paused`). PATCH /api/v2/new-relic-integrations/{new_relic_integration_id} Requires a Better Stack Incidents API token with access to the resource.
# Update on-call schedule event Update a single event in the given on-call schedule. Events starting sooner than today at 0:00 UTC can't be updated. PATCH /api/v2/on-calls/{schedule_id}/events/{event_id} Requires a Better Stack Incidents API token with access to the resource.
Tool to update an on-call schedule's name. Use when you need to rename an existing on-call calendar.
# Update outgoing e-mail Updates an existing outgoing e-mail integration. Only the parameters you send are changed. Returns the updated integration, or validation errors. Sending `recipients` replaces the whole recipient list. PATCH /api/v2/outgoing-emails/{integration_id} Requires a Better Stack Incidents API token with access to the resource.
Tool to update an existing outgoing webhook integration. Use when you need to modify the configuration of a webhook endpoint.
# Update PagerDuty integration Update an existing PagerDuty integration. Send only the parameters you wish to change (eg. `name`). PATCH /api/v2/pager-duty-webhooks/{pager_duty_webhook_id} Requires a Better Stack Incidents API token with access to the resource.
# Update Prometheus integration Update an existing Prometheus integration. Send only the parameters you wish to change (eg. `paused`). PATCH /api/v2/prometheus-integrations/{prometheus_integration_id} Requires a Better Stack Incidents API token with access to the resource.
Update a severity level (urgency) by ID, providing its name and SMS, call, email, and push notification settings.
Update an existing Slack integration's explicitly provided settings. Lists replace the whole list. Connect Slack in the Better Stack dashboard first.
# Update a source Updates an existing source. Send only the parameters you wish to change (e.g. `name` ) PATCH /api/v2/sources/{source_id} Requires a Telemetry API token with access to the resource.
Update an existing source group in Better Stack Logs/Telemetry. Use this to rename a source group or change its sort order. Requires a Telemetry API token (different from Uptime API token).
# Update Splunk integration Update an existing Splunk On-Call integration. Send only the parameters you wish to change (eg. `name`). PATCH /api/v2/splunk-on-calls/{splunk_on_call_id} Requires a Better Stack Incidents API token with access to the resource.
Tool to update an existing status page group. Use when you need to modify the name or display order of a status page group.
Tool to update an existing status page report. Use when you need to modify the title, timing, or affected resources of an existing incident or maintenance report.
Tool to update an existing status page resource. Use when you need to modify the display name, position, widget type, or other properties of a resource on a status page.
Tool to update an existing status page section. Use when reorganizing sections or changing their display. Leave name blank to hide the section header.
# Update status page subscriber Updates which status page resources an e-mail subscriber receives notifications for. Only `status_page_resource_ids` can be changed. To change an e-mail address, remove the old subscriber and create a new one. PATCH /api/v2/status-pages/{status_page_id}/subscribers/{subscriber_id} Requires a Better Stack Incidents API token with access to the resource.
Tool to update an existing status page configuration. Use when modifying settings like company info, appearance, access control, or display preferences.
Tool to update an existing status update for a status report. Use when you need to modify the message, affected resources, or other details of a previously created status update.
Change an existing team member's role using an ID from List roles. Supports custom roles, returned as role=custom. Requires a global API token with team_name, or a team-scoped Incidents API token. Changes to or from admin are forbidden; changes to or from billing_admin require a global token and apply across all the member's teams. Pending invitations cannot use this operation. Assigning the current role returns the member unchanged (HTTP 200).
Tool to update an existing urgency group (severity group). Use when you need to modify the name or sort order of a severity group.
The Better Stack integration connects your Dench AI CRM directly to Better Stack, so agents can read and act on your Better Stack data as part of everyday work — answering questions in chat, keeping your CRM in sync, and running automations without anyone copying data between tools.
311 actions are available for agents to invoke on your behalf. Every call runs through Better Stack's own authorization, scoped to the account you connect.
Sign in to your Dench workspace and open Integrations.
Find Better Stack and click Connect — you'll authorize access through Better Stack's own sign-in flow. No API keys or code required.
Ask an agent to use Better Stack in chat, or call it from an automation.
Manage or disconnect the connection any time from workspace settings.
The Dench Better Stack integration connects your AI CRM to Better Stack, so AI agents can work with your Better Stack data as part of chats, automations, and CRM workflows. You connect your account once, and every agent in your workspace can use it — governed by your workspace permissions.
The Better Stack integration currently exposes 311 actions, including Acknowledge Incident, Batch create catalog records, Batch remove catalog records, Batch update catalog records, Batch upsert catalog records, and Bulk update on-call events. Agents invoke them on your behalf from chat or from automations.
No. You connect Better Stack from your Dench workspace using Better Stack's own sign-in and authorization flow — no API keys to copy, no glue code to maintain.
Connections are authorized through Better Stack's own authentication flow, and Dench stores only the authorization needed to act on your behalf. You can review and disconnect the Better Stack connection from your workspace settings at any time.