Contents
Changelog
REMOVAL
Effective from:
July 1, 2020
Removal of
additional_data
and pagination
objects from 3 endpointsAnnounced: May 25, 2020
Effective from:
July 1, 2020
July 1, 2020
Removal of additional_data
and pagination
objects from 3 endpoints
additional_data
and pagination
objects from 3 endpointsWhat will change?
We have now deprecated and will be removing the additional_data
and pagination
objects on July 1, 2020 from the responses of the following Deal, Person and Organization endpoints.
Here is the list of 3 affected endpoints:
GET /persons/{id}/permittedUsers
GET /organizations/{id}/permittedUsers
GET /deals/{id}/permittedUsers
How the response body currently looks:
{
"success": true,
"data": [
007
],
"additional_data": {
"pagination": {
"start": 0,
"limit": 1,
"more_items_in_collection": false
}
}
}
Response body after the change:
{
"success": true,
"data": [
007
]
}
If your requests to those three endpoints also contain pagination related parameters limit
and start
we recommend removing those as they won’t serve their purpose any longer.
Who is affected?
Anyone with functionality built on top of the previous behaviour. For example, anyone who is strictly checking the shape of the response of the aforementioned 3 endpoints.
Published on May 25, 2020