Skip to main content

​
Overview

The get_status_page_post tool retrieves detailed information about a specific status page post, including its title, type, timeline, and updates.
This is a read-only tool that does not modify any data in your PagerDuty account.

​
Parameters

​
status_page_id
string
required
The unique identifier of the status page.Example: "PSTATUS1"
​
post_id
string
required
The unique identifier of the status page post.Example: "POST123"
​
include
array
Include additional related resources in the response. Options:
  • status_page_post_update - Include all post updates
Example: ["status_page_post_update"]

​
Response

Returns a detailed status page post object.
​
id
string
The unique identifier of the status page post
​
type
string
Always returns "status_page_post"
​
self
string
The API URL at which this post is accessible
​
post_type
string
The type of post. Options:
  • incident - An unplanned service disruption
  • maintenance - A planned maintenance window
​
status_page
object
Reference to the status page this post belongs to
​
title
string
The title of the post
​
starts_at
datetime
The date and time when the post becomes effective (for maintenance posts)
​
ends_at
datetime
The date and time when the post is concluded (for maintenance posts)
​
linked_resource
object
Reference to a linked resource (e.g., an incident)
​
postmortem
object
Reference to a postmortem document (if applicable)
​
updates
array
List of post updates (only included if requested via include parameter)

​
Example Usage

"Show me the details of status page post POST123"

​
Use Cases

  • Review incident communication - See what was communicated about an incident
  • Check maintenance schedule - View maintenance window timing and details
  • Audit post updates - Review the timeline of updates posted
  • Verify messaging - Confirm the content and status of communications
  • Track impact - See which services were reported as impacted

​
Response Example

{
  "id": "POST123",
  "type": "status_page_post",
  "post_type": "incident",
  "title": "API Latency Issues",
  "status_page": {
    "id": "PSTATUS1",
    "type": "status_page"
  },
  "starts_at": "2024-01-15T14:00:00Z",
  "ends_at": "2024-01-15T16:30:00Z",
  "updates": [
    {
      "id": "UPDATE1",
      "message": "We are investigating increased API latency",
      "status": {
        "id": "investigating"
      },
      "severity": {
        "id": "major"
      },
      "reported_at": "2024-01-15T14:00:00Z"
    },
    {
      "id": "UPDATE2",
      "message": "Issue has been resolved",
      "status": {
        "id": "resolved"
      },
      "severity": {
        "id": "major"
      },
      "reported_at": "2024-01-15T16:30:00Z"
    }
  ]
}

​
Post Types Explained

​
Incident

Represents an unplanned service disruption or degradation. Used to communicate ongoing issues to customers.

​
Maintenance

Represents a planned maintenance window. Used to notify customers of scheduled service interruptions.

Build docs developers (and LLMs) love

Get started for freeTalk to us