Deprecated Calls Removal
In addition to the reorganization of the API Reference and the deprecation announcement of a limited list of overlapping V4 operations, we are also announcing the end of service date of a number of operations that were already flagged as deprecated in the developers portal.
As these operations have been marked as deprecated a long time ago already, they see very little usage. Their removal will hardly impact your integrations.
The detailed explanation for deprecated operations use the old URL schemes (before the API Reference reorganization), as those are certainly the paths used in your code.
The new URL scheme of these deprecated V4 operations can be seen by clicking the links to the developers portal.
The equivalent replacements are always documented with the new URL schemes, as adaptations should be made with the up-to-date path.
Retrieve the results and error files of a mono file ETL
The operation to 'Get a single ETL execution's errors files' is a V5 call that allowed to retrieve the error file of an ETL excution.
> GET /v5/entities/{entity}/etl-executions/{executionId}/errors
It can be replaced by the V5 operation 'Get a single ETL execution's output files' that allows to retrieve both the error and the result file of this execution at once.
> GET /mass-imports/v5/entities/{entity}/etl-executions/{executionId}/output-files
The generation of both files depend on the result of the ETL and whether their generation is activated in the ETL definition.
The operation to 'Get a single mono file ETL execution's results' is a V5 call that was used before the development of multi file ETLs.
> GET /v5/entities/{entity}/etl-executions/{executionId}/results
It can be replaced by the V5 operation 'Get a single ETL execution's results', which works regardless of the number of files processed by the ETL.
> GET /mass-imports/v5/entities/{entity}/etl-executions/{executionId}/integration-results
Timing
The deprecated operations will continue working until December 2024.
E-mail and SMS campaign definition PUT methods
A series of operations to 'Set the HTML content', 'Set the personalization file' and 'Set the target file' of e-mail/SMS campaigns using the PUT method have deprecated since the inception of the equivalent operations with the POST method.
The following operations are getting removed, as the same routes with the POST method are used instead.
> PUT /v4/entity/{entity}/mail/{campaign}/content/body
> PUT /v4/entity/{entity}/mail/{campaign}/personalization
> PUT /v4/entity/{entity}/mail/{campaign}/target/list
> PUT /v4/entity/{entity}/sms/{campaign}/personalization
> PUT /v4/entity/{entity}/sms/{campaign}/target/list
Timing
The above operations have been flagged as deprecated for years and have seen zero usage recently.
They will be removed as of August 2025.
Old create a webhook on a profile/custom table
The operations to 'Create a webhook on a profile table' and 'Create a webhook on a custom table' have been flagged as deprecated since the inception of a generic operation to create webhooks, where the targeted events are defined in the body of the call.
The following operation are getting removed:
> POST /v4/entity/{entity}/table/{table}/webhookSubscription
> POST /v4/entity/{entity}/customTable/{table}/webhookSubscription
Their replacement is the generic operation
> POST /webhooks/v4/entity/{entity}/webhookSubscription
In this call, the elements to which the webhook is listening to are defined by the "on" parameter (e.g. "CUSTOM_TABLE" or "PROFILE_TABLE").
Timing
The above operations have been flagged as deprecated for years and have seen zero usage recently.
They will be removed as of August 2025.