Hi, I am currently using the OpenAPI specification provided in your YAML file to generate an API client for the /companies/list endpoint. According to the YAML, pagination is implemented via a "pages" object, which includes a "next" property defined as a starting_after_paging object. This object is expected to contain properties like per_page and starting_after.
However, the actual API response returns the "next" property as a plain URL string, for example:
"pages": {
"type": "pages",
"next": "https://api.intercom.io/companies/list?page=2&per_page=1&order=desc",
"page": 1,
"per_page": 1,
"total_pages": 223
},
"total_count": 223
I have verified that this behavior is consistent even when using the API testing tool provided at https://developers.intercom.com/docs/references/rest-api/api.intercom.io/companies/listallcompanies
Could you please clarify whether this is a known issue or an intentional change in the API implementation that has not yet been reflected in the YAML documentation? Any guidance on how to proceed—whether through an updated specification or a recommended workaround—would be greatly appreciated.
Thank you for your assistance.