Changelog
- API Reference
- Guide
AddedConfigurable duration for respondent activity exclusions
27 April 2026
The respondent activity exclusions duration is now configurable. You can specify how far back exclusion checks should look using a new duration field in ISO-8601 period format (date-based only, e.g. P30D, P2W, P3M, P1Y). Allowed values are between 1 and 396 days. If no duration is provided, the window defaults to P90D (90 days), preserving the previous behavior.
Updated endpoints:
- PUT
/demand/accounts/{account_id}/projects/{project_id}/target-groups/{target_group_id}/respondent-activity-exclusions— Request body now accepts an optionaldurationat the request level and on each item inrespondent_activity_exclusions. - POST
/demand/accounts/{account_id}/projects/{project_id}/target-groupsand PUT/demand/accounts/{account_id}/projects/{project_id}/target-groups/{target_group_id}— Inlinerespondent_activity_exclusionspayloads now supportdurationon each exclusion item when creating or updating a draft target group.
AddedRespondent activity exclusions
20 April 2026
You can now exclude respondents from entering a target group based on their participation history in other projects or target groups. Exclusions are evaluated dynamically at the moment a respondent attempts to enter a survey, enabling real-time overlap prevention for concurrent live studies.
Key capabilities:
- Unified API workflow: Pass an array of project and target group IDs in a single request to define multi-layered exclusions.
- Real-time enforcement: Exclusion checks happen at the point of entry, keeping your sample accurate for live studies.
- Automated 90-day window: Respondents with a Completed or In-client status in any excluded project or target group are automatically excluded for 90 days. Duration is not currently configurable.
New endpoints:
- GET
/demand/accounts/{account_id}/projects/{project_id}/target-groups/{target_group_id}/respondent-activity-exclusions— Retrieve the current respondent activity exclusion list for a target group. - PUT
/demand/accounts/{account_id}/projects/{project_id}/target-groups/{target_group_id}/respondent-activity-exclusions— Set the respondent activity exclusion list for a target group. Each request fully replaces the existing list.
Updated endpoints:
- POST
/demand/accounts/{account_id}/projects/{project_id}/target-groups— Supports settingrespondent_activity_exclusionsinline when creating a draft target group. - PUT
/demand/accounts/{account_id}/projects/{project_id}/target-groups/{target_group_id}— Supports settingrespondent_activity_exclusionsinline when updating a draft target group. - GET
/demand/accounts/{account_id}/projects/{project_id}/target-groups/{target_group_id}— Response now includes therespondent_activity_exclusionsfield.
Our configurable exclusions period will be out soon, which will allow you to make edits to the respondent activity exclusions duration period.
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.
BreakingNew Cint Exchange Demand API version 2025-12-18
18 December 2025
We're committed to continually enhancing the Cint Exchange Demand API to help you get to insights faster and more efficiently. Based on your feedback, the 2025-12-18 API version introduces improvements across design, structure, and performance.
Please use version 2025-12-18 to access the improvements outlined below.
New integration policy
The release of the Cint Exchange Demand API version 2025-12-18 introduces a new forward-only integration policy.
What is a forward-only integration
Once the 2025-12-18 version is used for a resource such as profiling, older API versions for the same resource will not be supported.
Why we are introducing this change
The new API version introduces advanced data structures, such as open-ended grouping, that are not compatible with legacy API versions. Updating a resource that has been created or modified using the newer version via older endpoints may lead to data inconsistencies, corruption, or integration errors. This policy helps preserve data integrity, ensures access to the full capabilities of the latest API version, and delivers a consistent, interchangeable experience.
What this means for you
If you begin using the Cint Exchange Demand API version 2025-12-18 for a specific resource, for example profiling, all subsequent create, write, or update operations for that resource must use the 2025-12-18 version of the API.
This approach ensures stability, data consistency, and long-term compatibility as the platform evolves.
How can you start integration?
Please contact your Cint integration consultant to learn more about our latest API version and how to enable access on your account.
Key changes
Profiling
New profiling features
- Group open-ended questions. This allows multiple free-text questions to be bundled under a single group instead of completely separate items. Example: product feedback grouping two questions such as "what did you like most about the product?" and "what did you like least about the product?"
- Apply a profile template to target group endpoints.
- Apply a profile template combined with your own profiling setup.
- Give quotas their own name using the
namefield to improve tracking.
Updated profiling features
- Interlocked profiles are no longer a standalone object and are now part of the profiling object known as "blended profiles".
- The target object is now the central piece that links questions, conditions, and quotas. Existing use of profiles will need to be refactored to accommodate the change.
- Property fields have been renamed to improve clarity:
filling_goal→completes_goalquota_percentage→completes_goal_percentagequota_nominal→completes_goalindex→conditionindexes→conditionsungrouped→targetgrouped→targetinterlocked_profiles→ now specified by the ENUM valueblendedwithinprofiles: []
- Endpoints have been renamed:
/apply-profiles→/manage-profiles/create_interlocked_profile→/create-blended-profile/generate-interlocked-profile→/generate-blended-profile/panel-distribution→/supplier-quota-distribution
Removed profiling endpoints
The endpoints below have been removed to accommodate the declarative profiles endpoint for launched target groups:
- PUT
https://api.cint.com/v1/demand/accounts/{account_id}/projects/{project_id}/target-groups/{target_group_id}/profiles/disable-quotas - GET
https://api.cint.com/v1/demand/accounts/{account_id}/projects/{project_id}/target-groups/{target_group_id}/profiles - POST
https://api.cint.com/v1/demand/accounts/{account_id}/projects/{project_id}/target-groups/{target_group_id}/profiles/:profile_id/convert-to-regular-profile - POST
https://api.cint.com/v1/demand/accounts/{account_id}/projects/{project_id}/target-groups/{target_group_id}/profiles/:profile_id/group-quotas
Example: New profile markup
"profiles": [
{
"object": "regular",
"id": "01JY5Q1GY7JWX1JHQH8D1W2N9Z",
"name": "birth gender",
"description": "¿Es usted…?",
"description_translated": "What is your gender?",
"quotas_enabled": true,
"targets": [
{
"id": "01JY5V5NDSVHG8S3FX63Y73K3F",
"text": "Hombre",
"text_translated": "Male",
"conditions": [
{
"object": "selection",
"question_id": 43,
"option": "1"
}
],
"quota": {
"name": "SF-BirthGender-Quota-1",
"completes_goal_percentage": 49.21,
"completes_goal": 492,
"completes": 0,
"prescreens": 0
}
}
]
}
]
Feasibility
Updated the feasibility endpoint to simplify calls by removing the requirement for project_id:
- Removed: POST
https://api.cint.com/v1/demand/accounts/{account_id}/projects/{project_id}/target-groups/calculate-feasibility - New endpoint: POST
https://api.cint.com/v1/demand/accounts/{account_id}/target-groups/calculate-feasibility
The supplier_ids: [] within the allocations: {} object now matches its usage across other endpoints.
General improvements
Updated error messages clarify what went wrong to increase clarity.
Additional changes
human_readable_idnow follows snake_case standard. Affected endpoint: GEThttps://api.cint.com/v1/demand/accounts/{account_id}/projects/{project_id}- Target group performance endpoint currency format updated to match all other endpoints:
"completes_cost": {"value": "2.7352", "currency_code": "USD", "currency_scale": null} client_cpirenamed toclient_cost_per_interview_noteto clarify it refers to a note, not the actual CPI.pricing_modelandtypeenum valueratecardchanged torate_card(snake_case). Affected endpoints:https://api.cint.com/v1/demand/accounts/{account_id}/projects/{project_id}/target-groups/{target_group_id}https://api.cint.com/v1/demand/accounts/{account_id}/projects/{project_id}/target-groups/{target_group_id}/overviewhttps://api.cint.com/v1/demand/accounts/{account_id}/business-units/{business_unit_id}/generate-price-prediction
Deprecated endpoints and attributes
- Removed feasibility endpoint (deprecated in
2025-05-27): POSThttps://api.cint.com/v1/demand/accounts/{account_id}/projects/{project_id}/target-groups/calculate-feasibility - Removed Exclusion endpoints (deprecated in
2025-05-27):- GET
https://api.cint.com/v1/demand/accounts/{account_id}/projects/{project_id}/target-groups/{target_group_id}/exclusions/cid - POST
https://api.cint.com/v1/demand/accounts/{account_id}/projects/{project_id}/target-groups/{target_group_id}/exclusions/cid - GET
https://api.cint.com/v1/demand/accounts/{account_id}/projects/{project_id}/target-groups/{target_group_id}/exclusions/rid - POST
https://api.cint.com/v1/demand/accounts/{account_id}/projects/{project_id}/target-groups/{target_group_id}/exclusions/rid
- GET
- Removed Download Report (deprecated from
2025-05-27): GEThttps://api.cint.com/v1/demand/accounts/{account_id}/reports/download - Removed
purchase_order_numberattribute (deprecated in2025-05-27). Affected endpoints: GET/POST/PUT project endpoints. - Removed
nameattribute (deprecated in2025-05-27). Affected endpoints: target-groups endpoints.
Next steps
If you already have an existing integration, please contact your Cint integration consultant for access to the latest version of the Cint Exchange Demand API.
If you're not yet integrated with the Cint Exchange Demand API, please contact your Cint integration consultant to learn more.
AddedConfigurable duration for respondent activity exclusions
27 April 2026
You can now configure how far back respondent activity exclusions look when filtering respondents. Previously, the exclusion window was fixed at 90 days; you can now set any duration between 1 and 396 days, either as a default for the whole request or per individual exclusion item. If no duration is provided, the window defaults to 90 days, so existing integrations are unaffected.
Updated how-to guides:
- Exclude respondents based on past activity — Now covers how to set request-level and item-level
durationvalues, including the precedence rules and how calendar-aware formats are normalized.
Updated deep dives:
- How respondent activity exclusions work — Explains the rolling exclusion window and how each excluded project or target group can use its own configured duration.
AddedRespondent activity exclusions
20 April 2026
You can now exclude respondents from entering a target group based on their participation history in other projects or target groups. New how-to guides and deep dives cover the full workflow, from understanding the exclusion model to configuring it via the API.
How-to guides:
- Exclude respondents based on past activity — Configure respondent activity exclusions on a target group via the dedicated endpoint or inline during target group creation.
Deep dives:
- What are respondent exclusions — An introduction to the three respondent exclusion rules available on the Cint Exchange and how they protect sample quality by filtering respondents before they enter a survey.
- Exclusion rule hierarchy — The fixed order in which respondent exclusion checks are evaluated when a respondent requests entry to a survey.
- Choosing an exclusion method — A comparison of all three exclusion methods by scope, complexity, and use case to help you pick the right one for your study.
- How respondent activity exclusions work — How the Cint Exchange evaluates respondent history at the point of entry and applies the 90-day rolling exclusion window.