What has been fixed?

It has come to our attention that up until now, supplying a new pipeline_id when updating a deal via the PUT /deals/{id} endpoint did not correctly update the stage_id associated with the deal’s pipeline.

Hence, on February 8, 2023, we implemented a fix to the behavior in our system. Updating the pipeline_id of a deal via the PUT /deals/{id} endpoint now automatically updates the associated stage_id value to the first stage of the specified pipeline.

As a reminder, the behavior of pipeline_id and stage_id for the PUT endpoint is as follows:

• pipeline_id - the ID of the pipeline this deal will be added to. By default, the deal will be added to the first stage of the specified pipeline.
• stage_id - the ID of the stage this deal will be added to. Please note that a pipeline will be assigned automatically based on the stage_id. If omitted, the deal will be placed in the first stage of the default pipeline.

What does it mean for me?

The bug has been fixed in our system and no further action is required to continue using the pipeline_id and/or stage_id body parameters for updating deals.

Should you notice an inconsistency between pipeline_id and stage_id values for existing deals that have been updated with the PUT endpoint, we suggest contacting our support.

In the case of any questions or comments, let us know in the Developer’s Community.