Skip to main content
Version: 2025-05-27

Changelog

[Added] Recontact specific respondents​

New endpoints and functionality to create surveys that target specific, pre-identified respondents from previous studies.

Release date: 31 July 2025

Endpoints: Recontacts endpoints

Update and functionality: 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.

[Added] Manage exclusion groups​

New endpoints to create, modify, and manage Exclusion Groups and associate target groups with them.

Release date: 31 July 2025

Endpoints:

View related 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

Update and Functionality: 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.

[Added] Increased limit for ID-Based exclusions to 100k​

Release date: 31 July 2025

Endpoints:

New

View related 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

[Deprecated] Legacy exclusion group APIs​

These endpoints are deprecated. They'll be supported for the lifetime of their respective API versions but will be removed in future releases.

View related 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

Update and Functionality: New endpoints raising 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 for uploading exclusion files of up to 100,000 IDs. The previous endpoints supporting up to 10,000 IDs are now deprecated and will be supported for the lifetime of their respective API versions but will be removed in future API versions.

Version: Deprecated from all available versions

[Updated] Feasibility endpoints now handle 100k completes​

Affected fields:

  • filling_goal

Release date: 10 June 2025

Endpoints: Feasibility endpoints

Update and Functionality: We have updated the feasibility endpoints based on your feedback. "filling_goal" field now allows up to 100,000 respondents where previously this was capped at 10,000 respondents. This does not yet apply to creating or managing target groups.

Version: Updated on all available versions

[Updated] Live URL and Test URL optional property for draft target groups​

Affected fields:

  • live_url
  • test_url

Release date: 10 June 2025

Endpoints:

  • POST /demand/accounts/{account_id}/projects/{project_id}/target-groups
  • PUT /demand/accounts/{account_id}/projects/{project_id}/target-groups/{target_group_id}

Update and Functionality: We have updated the draft target groups based on your feedback! The live_url and test_url fields are now optional for draft target groups. Note the live_url field must be set before the target group can be put into fielding

Version: Updated to all available versions

[Added] PUT and POST draft endpoint property updates​

Affected fields:

  • expected_incidence_rate
  • expected_length_of_interview_minutes
  • filling_goal
  • project_manager_id
  • collects_pii

Release date: 10 June 2025

Endpoints:

  • POST /demand/accounts/{account_id}/projects/{project_id}/target-groups
  • PUT /demand/accounts/{account_id}/projects/{project_id}/target-groups/{target_group_id}

Update and Functionality: These fields are no longer nullable and must be provided (required). This change improves consistency.

Version: Added to all available versions

[Deprecated] Get questions​

Release date: 12 May 2025

Endpoints:

  • GET /demand/questions?{queryParams}

Update and Functionality: We’ve deprecated this endpoint based on customer feedback.

Please use GET /demand/accounts/{account_id}/questions-translation

Version: Deprecated from all available versions

Release date: 12 May 2025

Endpoints:

  • GET /demand/questions/{question_id}

Update and Functionality: We’ve deprecated this endpoint based on customer feedback.

Please use GET /demand/accounts/{account_id}/questions-translation

Version: Deprecated on all available versions

[Added] Project Customer Reference Number​

Affected fields:

  • project_customer_reference_number

Release date: 8 May 2025

Endpoints: within the project endpoints

Update and Functionality: This allows you to capture your project-related identifiers, like purchase orders or job numbers.

Version: Added to all available versions

[Deprecated] Purchase Order Number​

Affected fields:

  • purchase_order_number

Release date: 8 May 2025

Endpoints: within the project endpoints

Update and Functionality: based on customer feedback and review. This field has caused some confusion and we have deprecated this field in favor of project_customer_reference_number.

Version: Deprecated from all available versions