What is changing?

New webhooks coverage for deal products, installments, and custom field definitions, plus a handful of smaller API improvements across deals, persons, organizations, and fields.

New webhooks types

Deal products: Get notified when products are added to, updated on, or removed from a deal. Useful for keeping order systems, billing, or quoting tools in sync without polling deal endpoints.

Deal installments: Get notified when installment schedules on deals are created, updated, or removed. Pairs naturally with deal product webhooks for revenue and billing workflows.

Entity field webhooks: You can now subscribe to webhooks that fire when custom field definitions change — not the values on records, but the schema itself. This is useful for keeping integration metadata, mappings, or generated types in sync when admins add, rename, or delete fields. Available for:

• Deal fields
• Lead fields
• Person fields
• Organization fields
• Product fields
• Project fields

Other webhooks improvements

Organization webhooks now include additional fields where applicable: website, linkedin, industry, annual_revenue, and employee_count. These appear automatically in payloads when the relevant features are enabled on the account.

Other API improvements

• include_labels and include_option_labels query parameters on GET /api/v2/deals, GET /api/v2/persons, and GET /api/v2/organizations — include_labels adds a labels array of { id, label } objects to the response alongside the existing label_ids. include_option_labels resolves option IDs on single- and multi-option custom fields to their human-readable labels.
• is_writable flag is now exposed on field definitions in the Fields API v2, so you can tell programmatically which fields can be written to when using the relevant entity's POST and PATCH endpoints.
• Custom field validation errors now include the field_code on v2 deal, person, and organization create/update endpoints — so when a payload with many custom_fields fails, you can tell exactly which field was invalid instead of just getting a generic "Validation failed" message.
• New include_field_code query parameter on the v1 Filters API — when set to true, each filter condition in the response includes its field_code, making it easier to map filters to field definitions.
• Documented task_id support in notes endpoints — you can attach notes to project tasks via the existing notes API.

Additional resources:

See the Webhooks v2 documentation for more details.

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