Update on new entity count limits for a set of features

What is changing?

The format of the text in the error response field is being updated for entity count limits that were announced previously in this changelog update.

Affected endpoints:

• POST /v1/activityTypes
• POST /v1/dealFields
• PUT /v1/dealFields/{id}
• POST /v1/organizationFields
• PUT /v1/organizationFields/{id}
• POST /v1/personFields
• PUT /v1/personFields/{id}
• POST /v1/productFields
• PUT /v1/productFields/{id}
• POST /v1/deals/{id}/products
• POST /v1/filters
• POST /v1/tasks
• PUT /v1/tasks/{id}
• POST /v1/organizationRelationships
• PUT /v1/organizationRelationships/{id}

Here's an example of the 403 error response for POSTrequest:

{
  "success": false,
  "error": "Couldn't add activity type. You've reached the activity type per company limit.",
  "error_info": "Please check developers.pipedrive.com for more information about Pipedrive API",
  "data": null,
  "additional_data: null
}

Here's an example of the 403 error response for PUTrequest:

{
  "success": false,
  "error": "Couldn't add activity type. You've reached the activity type per company limit.",
  "error_info": "Please check developers.pipedrive.com for more information about Pipedrive API",
  "data": null,
  "additional_data: null
}

Why it is changing?

This update aims to improve clarity and provide a better user experience by enhancing the wording in error messages.

If you have any questions or comments, feel free to let us know in the Developer’s Community.