Changelog
- API Reference
- Guide
AddedPrivate exchange CPI added to target-group-updated webhook
27 January 2026
private_exchange_cpi_change added to the target-group-updated webhook to notify when there are changes to cost per interview (CPI) for private exchanges.
Endpoints: target-group-updated webhook
Version: Added to releases from 2025-05-27 onwards.
AddedRecontact specific respondents
31 July 2025
New endpoints and functionality to create surveys that target specific, pre-identified respondents from previous studies.
Endpoints: Recontacts endpoints
You can now create a target group with "study_type": "recontact" to run surveys exclusively for a specified list of respondent IDs. This feature is ideal for longitudinal studies and re-engaging participants. Key requirements:
- You'll need to make a separate API call to upload and manage respondent IDs after creating the draft target group.
- The
[%RECONTACT_RSID%]variable must be included in your live URL. - The contents found within Cint's recontact global allocations template must be used:
"template_id": "01JH0PEGPC4Z8RDD304E2SF0EW" - Adding further profiling to recontact surveys is not supported.
Version: Added to releases from 2025-05-27 onwards.
AddedManage exclusion groups
31 July 2025
New endpoints to create, modify, and manage Exclusion Groups and associate target groups with them.
Endpoints:
- GET
/demand/accounts/{account_id}/exclusion-groups - POST
/demand/accounts/{account_id}/exclusion-groups - GET
/demand/accounts/{account_id}/exclusion-groups/{exclusion_group_id} - DELETE
/demand/accounts/{account_id}/exclusion-groups/{exclusion_group_id} - PUT
/demand/accounts/{account_id}/exclusion-groups/{exclusion_group_id} - GET
/demand/accounts/{account_id}/exclusion-groups/{exclusion_group_id}/target-groups - POST
/demand/accounts/{account_id}/exclusion-groups/{exclusion_group_id}/target-groups/add - POST
/demand/accounts/{account_id}/exclusion-groups/{exclusion_group_id}/target-groups/remove - GET
/demand/accounts/{account_id}/target-groups/{target_group_id}/exclusion-groups
Group multiple target groups, even across different projects, into a single reusable Exclusion Group. Any respondent completing a survey in one of the associated target groups is automatically excluded from all others in the group.
Version: Added to releases from 2025-05-27 onwards.
AddedIncreased limit for ID-based exclusions to 100k
31 July 2025
The limit for Respondent ID and Access Respondent GUID exclusions on a single target group has increased from 10,000 to 100,000. New endpoints support uploading exclusion files of up to 100,000 IDs.
New endpoints:
- GET
/demand/accounts/{account_id}/projects/{project_id}/target-groups/{target_group_id}/exclusions/access-respondent-guid/paginated - POST
/demand/accounts/{account_id}/projects/{project_id}/target-groups/{target_group_id}/exclusions/jobs/upload-respondents-by-file - GET
/demand/accounts/{account_id}/projects/{project_id}/target-groups/{target_group_id}/exclusions/jobs/remove-all-respondents/{job_id} - POST
/demand/accounts/{account_id}/projects/{project_id}/target-groups/{target_group_id}/exclusions/jobs/upload-respondents-by-file - GET
/demand/accounts/{account_id}/projects/{project_id}/target-groups/{target_group_id}/exclusions/jobs/upload-respondents-by-file/{job_id} - GET
/demand/accounts/{account_id}/projects/{project_id}/target-groups/{target_group_id}/exclusions/rsid/paginated
Version: Added to 2025-02-17 and 2025-05-27 API versions.
DeprecatedLegacy exclusion group APIs
31 July 2025
These endpoints are deprecated. They'll be supported for the lifetime of their respective API versions but will be removed in future releases.
Deprecated endpoints:
- GET
/demand/accounts/{account_id}/projects/{project_id}/target-groups/{target_group_id}/exclusions/cid - POST
/demand/accounts/{account_id}/projects/{project_id}/target-groups/{target_group_id}/exclusions/cid - GET
/demand/accounts/{account_id}/projects/{project_id}/target-groups/{target_group_id}/exclusions/rid - POST
/demand/accounts/{account_id}/projects/{project_id}/target-groups/{target_group_id}/exclusions/rid
Version: Deprecated from all available versions.
ChangedFeasibility endpoints now handle 100k completes
10 June 2025
Affected fields: filling_goal
Endpoints: Feasibility endpoints
The filling_goal field now allows up to 100,000 respondents, where previously this was capped at 10,000. This does not yet apply to creating or managing target groups.
Version: Updated on all available versions.
ChangedLive URL and Test URL optional for draft target groups
10 June 2025
Affected fields: live_url, test_url
Endpoints:
- POST
/demand/accounts/{account_id}/projects/{project_id}/target-groups - PUT
/demand/accounts/{account_id}/projects/{project_id}/target-groups/{target_group_id}
The live_url and test_url fields are now optional for draft target groups. Note: live_url must be set before the target group can be put into fielding.
Version: Updated on all available versions.
AddedPUT and POST draft endpoint property updates
10 June 2025
Affected fields: expected_incidence_rate, expected_length_of_interview_minutes, filling_goal, project_manager_id, collects_pii
Endpoints:
- POST
/demand/accounts/{account_id}/projects/{project_id}/target-groups - PUT
/demand/accounts/{account_id}/projects/{project_id}/target-groups/{target_group_id}
These fields are no longer nullable and must be provided (required). This change improves consistency.
Version: Added to all available versions.
DeprecatedGet questions
12 May 2025
Endpoints:
- GET
/demand/questions?{queryParams} - GET
/demand/questions/{question_id}
These endpoints have been deprecated based on customer feedback. Please use GET /demand/accounts/{account_id}/questions-translation instead.
Version: Deprecated from all available versions.
AddedProject Customer Reference Number
8 May 2025
Affected fields: project_customer_reference_number
Endpoints: Project endpoints
Allows you to capture your project-related identifiers, such as purchase orders or job numbers.
Version: Added to all available versions.
DeprecatedPurchase Order Number
8 May 2025
Affected fields: purchase_order_number
Endpoints: Project endpoints
Deprecated in favor of project_customer_reference_number to reduce confusion. This field has been deprecated based on customer feedback and review.
Version: Deprecated from all available versions.
No updates for this version.