OnCallPagingApi Missing endpoint to list pages

Open

#2,773 opened on Aug 16, 2025 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty: 4/5
Estimated time: 3-5 days
Newbie friendliness: 35/100

Issue type: Feature
Clarity: Mostly clear
Activity status: Stale
Tech stack: openapi, python
Domain: api

Research direction

Start with src/datadog_api_client/v2/api/on_call_paging_api.py, especially the existing acknowledge-on-call-page example and endpoint. Compare the client API with the unstable web UI endpoint at /api/unstable/on-call/pages. Done means the client exposes a listing method under the unstable feature flag with the requested filtering support.

Written by the indexing model from the issue text.

Description

kind/bug stale

Describe the bug
OnCallPagingApi has methods to Escalate, Acknowledge, Resolve or Create On-Call Pages but not to list them.
The only way to list them is through the web ui https://app.datadoghq.eu/on-call/pages

To Reproduce
Steps to reproduce the behavior:

Try out the example for acknowledging an on-call page found here
Try to change the code to list current triggered pages
No methods or api endpoints exposed for that.

Expected behavior
A method similar to acknowledge_on_call_page but for listing outstanding pages, with the ability to filter out by responder, status, etc...

Screenshots

Environment and Versions (please complete the following information):

datadog-api-client==2.41.0

Additional context
The web UI is currently using an unstable API endpoint that differs from what the library is using ie:

The library: https://github.com/DataDog/datadog-api-client-python/blob/22e917aa5ba86e8dbd8f4f3b4b211c565138e615/src/datadog_api_client/v2/api/on_call_paging_api.py#L32
The web UI: https://app.datadoghq.eu/api/unstable/on-call/pages

If the endpoints is unstable the expected behavior is to have it supported under the unstable feature flag

Dominant language: Python
Stars: 166
Forks: 55
Avg merge: 2d 17h
Merged PRs (30d): 73

Contributor guide

Open the contributing guide

First steps

Read the whole issue, then the project's contributing guide.
Comment on the issue to say you are picking it up — it saves two people doing the same work.
Fork the repository and make your change on a branch.
Open a pull request that references the issue number.

Similar issues

[essnmx] Fix typo in NXLauetof application definition Open

essnmx good first issue

Difficulty 1/5 Under an hour Newbie friendliness 95/100

scipp/ess#760 · Opened Sep 23, 2026
[Feature] 奇物选择添加优先级 Open

Difficulty 2/5 1-3 hours Newbie friendliness 65/100

syfoud/Simulated_Scepter#174 · Opened Sep 23, 2026
garak adapter grades a NaN detector score as PASS Open

Difficulty 2/5 1-3 hours Newbie friendliness 75/100

Giskard-AI/giskard-oss#2840 · 1 comment · Opened Sep 23, 2026
A claim comment carrying the issue number is silently declined while the workflow reports success Open

area: repo bug perceived difficulty: 2

Difficulty 2/5 1-3 hours Newbie friendliness 70/100

Nitjsefnie-Harness-Commons/daedalus#926 · Opened Sep 23, 2026
`IOCExtractor` always fails: `ioc_analyzer.build()` takes 1 argument but the agent dispatcher passes 2 Open

Difficulty 2/5 1-3 hours Newbie friendliness 75/100

yeti-platform/yeti#1380 · Opened Sep 23, 2026

More Python issues