We have now deprecated and will be removing three response fields and a body parameter from the Users API to adhere to the global user management model.

The change is related to the Improvements to PermissionSets API and Users API and the Removal of the is_admin response field from Users API announcements.

What is changing?

1. We have deprecated and will soon be removing the following response fields from six endpoints of the Users API:
• signup_flow_variation
• modified: This field will be included in the response only if the user associated with the request has account settings access.
• phone: This field will be removed for all users, except for the phone number owner.

The user associated with the request can only see their own phone number in the response, but not other users’ phone numbers, regardless of the user’s access level.

Affected endpoints:

• GET /users
• GET /users/find
• GET /users/me
• GET /users/{id}
• POST /users
• PUT /users/{id}
2. From the POST /users endpoint, we have deprecated the name body parameter and it has now been made optional.

As an alternative to providing a name with the request, the user’s name can initially be filled by the provided e-mail address. The user can specify the name themselves when they accept their e-mail invitation to Pipedrive.

We strongly advise you to avoid using these deprecated fields as they will be removed on February 9, 2023.

Why is it changing?

We are introducing the granularity of user access rights under 5 specific categories: Deals app, Projects app, Campaigns app, Global Permissions, and Account Settings. Each category has its own permission set where you can grant users either the admin or regular access level.

We are removing the response fields and body parameter, because they either do not serve their purpose any more or they do not accommodate the new access model. The change aims to ensure consistency between the Pipedrive API and web app as well as increase the user’s privacy control opportunities.

Who will be affected?

Everyone who is using the fields mentioned above.

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