Explore documentation
  1. Welcome to Uptime 👋
  2. Frequently Asked Questions
  3. Monitoring
    1. Get started with monitoring
    2. Working with monitors
    3. Customizing monitors
    4. Monitor types
  4. On-call scheduling and alerting
    1. Get started with on-call
    2. Sending alerts to Slack ↗
    3. Connecting external calendars
    4. Advanced on-call setup
  5. Incidents
    1. Working with incidents
    2. Create incidents manually
    3. Post mortems
    4. Incident silencing
    5. Incident metadata
  6. Status pages
    1. Get started with status pages
    2. Working with status pages
  7. Integrations
    1. Integrating with Better Stack
  8. Team and account management
    1. Team management
    2. Account settings
    3. Audit logs
    4. Migrating to pay as you go
  9. API
    1. Get started with API
  10. Monitors API
    1. Monitors
    2. Monitor groups
    3. Heartbeats
    4. Heartbeat groups
  11. On-call & Incidents API
    1. On-call calendar
    2. On-call calendar events
    3. Escalation policies
    4. Escalation policy groups
    5. Severities
    6. Severity groups
    7. Incidents
    8. Comments
  12. Integrations API
    1. New Relic Integrations
    2. Datadog Integrations
    3. AWS CloudWatch Integrations
    4. Azure Integrations
    5. Google Monitoring Integrations
    6. Grafana Integrations
    7. Prometheus Integrations
    8. Email integrations
    9. Incoming webhooks
      1. List all incoming webhooks GET
      2. Get a single incoming webhook GET
      3. Create an incoming webhook POST
      4. Update an incoming webhook PATCH
      5. Delete an incoming webhook DELETE
      6. Incoming webhooks API response params
    10. Slack Integrations
    11. Splunk On-Call integrations
    12. PagerDuty Integrations
  13. Status pages API
    1. Status pages
    2. Status page sections
    3. Status page resources
    4. Status page reports
    5. Status page report updates
  14. Other API
    1. Metadata

Incoming webhooks API response params

Response body parameters

Namespace data

Parameter Type Value
id String The ID of the incoming webhook. String representation of a number.
type String incoming_webhook
attributes Object Attributes object. Contains all the incoming webhook attributes. See below.
attributes.name String Name of the incoming webhook.
attributes.created_at String (ISO DateTime format) When was the incoming webhook created.
attributes.updated_at String (ISO DateTime format) When was the incoming webhook last updated.
attributes.policy_id String ID of the escalation policy associated with the incoming webhook. String representation of a number.
attributes.team_name String The team this integration belongs to.
attributes.call Boolean Call the on-call person.
attributes.sms Boolean Send an SMS to the on-call person.
attributes.email Boolean Send an email to the on-call person.
attributes.push Boolean Send a push notification to the on-call person.
attributes.team_wait Integer How long we wait before escalating the incident alert to the team. In seconds.
attributes.recovery_period Integer How long the alert must be up to automatically mark an incident as resolved. In seconds.
attributes.url String What's the URL we expect incoming webhooks on.
attributes.paused Boolean Whether is the incoming webhook paused.
attributes.started_rule_type String Should an incident be started for all incoming webhooks, those satisfying all acknowledged_rules, or those satisfying any of them. Valid values are unused, all, or any.
attributes.acknowledged_rule_type String Should an incident be acknowledged for all incoming webhooks, those satisfying all acknowledged_rules, or those satisfying any of them. Valid values are unused, all, or any.
attributes.resolved_rule_type String Should an incident be resolved for all incoming webhooks, those satisfying all acknowledged_rules, or those satisfying any of them. Valid values are unused, all, or any.
attributes.started_rules.[] Rule Array of started rules. See Rule section below for attribute details.
attributes.acknowledged_rules.[] Rule Array of acknowledged rules. See Rule section below for attribute details.
attributes.resolved_rules.[] Rule Array of resolved rules. See Rule section below for attribute details.
attributes.cause_field Field How to extract an incident cause. See Field section below for attribute details.
attributes.title_field Field or null How to extract a customized incident title. See Field section below for attribute details. Send null to remove the field and use default title.
attributes.started_alert_id_field Field When starting an incident, how to extract an alert id, a unique alert identifier which will be used to acknowledge and resolve incidents. See Field section below for attribute details.
attributes.acknowledged_alert_id_field Field When acknowleding an incident, how to extract an alert id, a unique alert identifier which will be used to acknowledge and resolve incidents. See Field section below for attribute details.
attributes.resolved_alert_id_field Field When resolving an incident, how to extract an alert id, a unique alert identifier which will be used to acknowledge and resolve incidents. See Field section below for attribute details.
attributes.other_started_fields.[] Field Array of additional fields that will be extracted when incident is created. See Field section below for attribute details.
attributes.other_acknowledged_fields.[] Field Array of additional fields that will be extracted when incident is acknowledged. See Field section below for attribute details.
attributes.other_resolved_fields.[] Field Array of additional fields that will be extracted when incident is resolved. See Field section below for attribute details.

Rule

Parameter Type Value
created_at String (ISO DateTime format) When was the rule created.
updated_at String (ISO DateTime format) When was the rule last updated.
rule_target String The target of the rule. Can be any of the following: query_string, header, body, json, or xml.
match_type String The type of the rule. Can be any of the following: contains, contains_not, matches_regex, matches_regex_not, equals, or equals_not.
target_field String The target field of the rule.
content String The content we should match to satisfy the rule. Should be a valid Regex when match_type is match_regex.

Field

Parameter Type Value
name String The name of the field.
special_type String A special type of the field. Can be alert_id or cause or otherwise null for a custom field.
field_target String The target of the field. Can be any of the following:query_string, header, body, json, or xml.
match_type String The match type of the field. Can be any of the following: match_before, match_after, match_between, match_regex, or match_everything.
target_field String The target field of the field.
content String How should we extract content the field. Should be a valid Regex when match_type is match_regex.
content_before String When should we start extracting content for the field. Should be present when match_type is either match_between or match_before.
content_after String When should we start extracting content for the field. Should be present when match_type is either match_between or match_after.

Previous article

Delete an incoming webhook

Next article

List all Slack integrations