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.

Can I limit what my agent is allowed to do with the PagerTree API?

Yes. Because you run Jentic One yourself, your own rules decide which PagerTree operations and credentials your agent may use. Since PagerTree puts the alert id in the URL path, such as POST /alerts/{id}/acknowledge and POST /alerts/{id}/comments, you can scope the agent to a single alert and let it acknowledge or comment on that alert and nothing else. Operations like POST /alerts/{id}/resolve or POST /integrations stay off limits unless you explicitly grant them.