GET /servicedesk/{id}/customer returns fewer customers than the JSM Customers page shows

[PranayChhibber]

The Get customers API for our service desk returns far fewer customers than the Customers page in the JSM project.

Endpoint used

GET https://<>.atlassian.net/rest/servicedeskapi/servicedesk/36/customer?start=0&limit=50

What we see

• API response: size: [13], isLastPage: true. There is no next page.
• Project settings → Customers page in the UI: [50] customers.
• Difference: [37] customers appear in the UI but not in the API response.

The 13 returned customers are the first 13 rows of the UI list. Every customer after that is missing, including customers with a visible email address.We also tried the same call as a logged-in user and via a Forge app, with the same result.

Expected behaviour

The API should return every customer shown on the project’s Customers page, or the documentation should explain which customers are excluded and why.

[Mihai_leanzero]

Hi @PranayChhibber,

Not a paging cap. A capped page would come back with isLastPage: false. Atlassian has the gap itself on file as JSDCLOUD-18992, at Gathering Interest:

Engineering has confirmed this endpoint does not meet the requirement of retrieving the complete customer list programmatically.

Neither the ticket nor the reference says which customers get dropped. Not reproduced on our side, the test desk is too small to show it. Still experimental btw (412 there without X-ExperimentalApi: opt-in).

The thing I’d check is who makes the call. A 2022 changelog entry (CHANGE-668) opened the endpoint to customer accounts, and for those the results follow the project’s customer sharing settings. Was the logged-in user an agent or admin, and was the Forge call asApp() or asUser()?