You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This reference expects pagination.page and not pagination.per_page as it is a reference of the next page.
The two must be decoupled.
Expected
We would expect to have pagination.per_page instead of pagination.page in the OpenAPI spec.
Reproduction Steps
N/A.
The text was updated successfully, but these errors were encountered:
yacinehmito
changed the title
[Schema Inaccuracy] In _SearchContacts_, pagination.per_page is not defined.
[Schema Inaccuracy] In SearchContacts, pagination.per_page is not defined.
Aug 7, 2023
Schema Inaccuracy
There is an inconsistency between the schema of SearchContacts and what is documented in the API docs:
API docs documentation states that the
pagination.per_page
is to be provided in the request body to specify the number of items to return.However, both v2.9 and Unstable do not include this property, and instead define
pagination.page
.See the following lines (for v2.9):
Intercom-OpenAPI/descriptions/2.9/api.intercom.io.yaml
Lines 14873 to 14885 in 2498a89
Intercom-OpenAPI/descriptions/2.9/api.intercom.io.yaml
Lines 15143 to 15153 in 2498a89
I tested real API calls with both
pagination.per_page
andpagination.page
and the former is the one that works as expected; the latter has no effect.starting_after_paging
, which is relied on forpagination
of SearchContacts ' request body, also appear here:Intercom-OpenAPI/descriptions/2.9/api.intercom.io.yaml
Line 13547 in 2498a89
This reference expects
pagination.page
and notpagination.per_page
as it is a reference of the next page.The two must be decoupled.
Expected
We would expect to have
pagination.per_page
instead ofpagination.page
in the OpenAPI spec.Reproduction Steps
N/A.
The text was updated successfully, but these errors were encountered: