Pipedrive introduces Fields API v2 for managing custom fields

On December 10, 2025, Pipedrive released a Fields API v2 for managing custom fields across multiple entity types. Deal, person, organization and product fields support create, read, update and delete, and option lists on enum and set fields can be added, updated and removed in bulk. Activity fields can be listed and retrieved. The entry lists separate endpoint groups for activity, deal, person, organization and product fields. Each writable entity supports GET, POST, PATCH and DELETE on individual fields by field code, and POST, PATCH and DELETE on that field's options.

The details

• Effective from December 10, 2025.
• Endpoints use field_code identifiers, for example /api/v2/dealFields/{field_code}.
• Bulk options endpoints support POST, PATCH and DELETE on enum and set fields.
• Activity fields are read-only in the listed endpoints.

Context

The Fields API v2 arrived a week before Pipedrive's app became available in ChatGPT on December 17, 2025. Pipedrive later added an is_writable flag to Fields API v2 definitions on May 21, 2026, and moved deprecated v1 endpoints out of support on August 1, 2026. Pipedrive also appointed Regi Vengalil as chief financial officer on December 2, 2025.

Not disclosed

• Whether v1 field endpoints are scheduled for deprecation
• Limits on the number of custom fields per entity