PagerTree API

Name: PagerTree API API
Brand: PagerTree API
Availability: InStock

✓ Official Vendor SpecIncident ManagementAlertingbearer22 EndpointsREST

For Agents

Manage PagerTree alerts, teams, schedules, escalation policies, integrations, and users with state transitions and on-call workflows.

Connect the PagerTree API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the PagerTree API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.

Install Jentic One Beta (Self-Hosted)

Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh

Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
jentic register       # connects your agent to your Jentic One instance

Jentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.

Capabilities

What an agent can do with PagerTree API API.

Create, read, update, and delete alerts with urgency levels and metadata

Transition alert states via acknowledge, reject, and resolve actions

Comment on alerts to add context and collaboration

Manage teams with members, admins, and escalation policy bindings

GET STARTED

Start building with PagerTree API API

Explore with Jentic

View OpenAPI Document

The PagerTree API is organized around REST for managing alerts, teams, schedules, escalation policies, integrations, and users. It supports creating, reading, updating, and deleting alerts with state transitions (acknowledge, reject, resolve), managing on-call schedules with time-window events, configuring team memberships and escalation policies, setting up integrations for alert ingestion, and managing user notification preferences. Returns JSON-encoded responses and uses standard HTTP verbs and status codes. Does not support bulk updates.

Use Cases

Patterns agents use PagerTree API API for, with concrete tasks.

★ Incident Response Workflow

SRE teams can automate incident response by creating alerts via POST /alerts with urgency and destination teams, then transitioning alert states through acknowledge, resolve, or reject actions. GET /alerts lists paginated alerts, and POST /alerts/{id}/comments adds collaboration notes. Combined with /teams/{id}/current_oncall, responders can route alerts to the on-call engineer and track resolution progress, building an automated incident management pipeline.

POST /alerts with title, urgency, and destination_team_ids to create an alert, then POST /alerts/{id}/acknowledge to accept it, add comments via POST /alerts/{id}/comments, and POST /alerts/{id}/resolve when fixed.

On-Call Schedule Management

Operations teams can programmatically manage on-call rotations by creating schedules via POST /schedules and querying on-call attendees via GET /schedules/{id}/current_oncall or GET /schedules/{id}/window_events with start/end times. GET /teams/{id}/current_oncall returns the current on-call team members. This enables automated on-call dashboards, shift notifications, or integration with calendar systems for visibility into who is responsible at any given time.

POST /schedules with a name to create a schedule, then GET /schedules/{id}/current_oncall to see who is on-call now, or GET /schedules/{id}/window_events with start and end query parameters to list on-call periods.

Monitoring Tool Integration

DevOps platforms can integrate alert sources like Datadog, Prometheus, or custom monitors by creating integrations via POST /integrations with urgency, integration_type_id, and destination team_ids. Each integration generates a webhook URL for the external tool to post alerts. GET /integrations lists configured integrations, and PUT /integrations/{id} updates routing or urgency. This centralizes alert ingestion from multiple monitoring tools into a unified incident workflow.

POST /integrations with name, urgency, integration_type_id, and team_ids to create an integration, then configure the external monitoring tool to send alerts to the generated webhook URL.

Key Endpoints

22 endpoints — the pagertree api is organized around rest for managing alerts, teams, schedules, escalation policies, integrations, and users.

METHOD

PATH

DESCRIPTION

POST

/alerts

Create an alert

POST

/alerts/{id}/acknowledge

Acknowledge an alert

POST

/alerts/{id}/resolve

Resolve an alert

POST

/alerts/{id}/comments

Comment on an alert

GET

/teams/{id}/current_oncall

Get team's current on-call users

POST

/schedules

Create a schedule

GET

/schedules/{id}/current_oncall

Get schedule's current on-call

GET

/schedules/{id}/window_events

List on-call events in a time window

POST

/integrations

Create an integration

POST

/alerts

Create an alert

POST

/alerts/{id}/acknowledge

Acknowledge an alert

POST

/alerts/{id}/resolve

Resolve an alert

POST

/alerts/{id}/comments

Comment on an alert

GET

/teams/{id}/current_oncall

Get team's current on-call users

Why though Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

PagerTree API keys are stored encrypted in the Jentic vault and injected as the Authorization bearer header at execution time. Keys never appear in agent prompts, transcripts, or response payloads.

Intent-based discovery

Agents search by intent such as 'create a pagertree alert' or 'get current on-call users' and Jentic returns the matching endpoint with its schema and required parameters.

Time to first call

Direct PagerTree integration: 2-3 days to model alerts, teams, schedules, integrations, and state transitions. Through Jentic: under 1 hour — search, load schema, execute.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Alternative

PagerDuty API

PagerDuty offers enterprise-grade incident management with advanced analytics and integrations.

Use PagerDuty for large enterprises with complex escalation needs; use PagerTree for simpler on-call management.

Alternative

Opsgenie API

Opsgenie provides incident management and on-call scheduling with Atlassian integration.

Use Opsgenie for Atlassian-centric teams; use PagerTree for standalone on-call management.

Alternative

VictorOps API

VictorOps (now Splunk On-Call) offers incident management with timeline visualization.

Use VictorOps for Splunk integrations; use PagerTree for REST-based on-call workflows.

FAQs

Specific to using PagerTree API API through Jentic.

What authentication does the PagerTree API use?

The PagerTree API uses bearer token authentication. Obtain an API key from your User Settings page and pass it in the Authorization header as 'Bearer <api_key>'. Through Jentic, keys are stored encrypted and injected automatically at execution time.

Can I query who is currently on-call?

Yes. GET /teams/{id}/current_oncall returns the current on-call users for a team, and GET /schedules/{id}/current_oncall returns the on-call attendees for a schedule at the current time.

How do I transition alert states?

Use POST /alerts/{id}/acknowledge to acknowledge an alert, POST /alerts/{id}/resolve to resolve it, or POST /alerts/{id}/reject to reject it. Each action requires the alert to be in a valid state (e.g., resolve requires open, dropped, or acknowledged state).

Does the API support bulk updates?

No. The PagerTree API does not support bulk updates. You must make individual requests for each alert, team, schedule, integration, or user operation.

Can I retrieve on-call schedules for a specific time range?

Yes. GET /schedules/{id}/window_events with start and end query parameters returns on-call attendees for the specified time window.

How do I integrate monitoring tools like Datadog?

Create an integration via POST /integrations with the appropriate integration_type_id and destination team_ids. The response includes a webhook URL that you configure in your monitoring tool to send alerts to PagerTree.