Changelog
- API Reference
- Guide
Addedproject-updated webhook
6 November 2026
Endpoints: List all available webhook event types, Create a webhook, Update an existing project
You can now subscribe to the project-updated event to be notified when a project of your account is updated, instead of polling Get an existing project by ID.
Key details:
- The event-types endpoint now lists
project-updated. - The envelope
typeiscom.cint.project.updatedand thedataschemaishttps://developer.cint.com/schemas/project-updated/v1. datacarries the project after the update:account_id,project_id,name,project_manager_id,project_customer_reference_number, andversion.project_manager_idandproject_customer_reference_numberare absent when the project has none.- The event is sent for every successful update, including updates made in Cint Exchange and by other API clients, and updates that don't change any field. Creating a project doesn't send it.
versionis the project's version after the update, the same number as in the project'sETag. Each project has its ownversion: keep the highest one you've applied for eachproject_idand ignore events for that project with a lower or equalversion. Every event carries the whole project, so the latest one is all you need.
Addedproject-created webhook
6 November 2026
Endpoints: List all available webhook event types, Create a webhook, Create a new project
You can now subscribe to the project-created event to be notified when a project is created in your account, instead of polling for new projects.
Key details:
- The event-types endpoint now lists
project-created. - The envelope
typeiscom.cint.project.createdand thedataschemaishttps://developer.cint.com/schemas/project-created/v1. datacarries the project as created:account_id,project_id,name,project_manager_id,project_customer_reference_number, andversion, which is always0.project_manager_idandproject_customer_reference_numberare absent when the project has none.- The event is sent once for each project created in your account, including projects created in Cint Exchange and by other API clients. Use
project_idto process each project once.
Addedreport-ready webhook
6 November 2026
Endpoints: List all available webhook event types, Create a webhook
You can now subscribe to the report-ready event to be notified when a report finishes generating, instead of polling the report status endpoint.
Key details:
- The event-types endpoint now lists
report-ready. - The envelope
typeiscom.cint.report.readyand thedataschemaishttps://developer.cint.com/schemas/report-ready/v1. datacarriesreport_id,account_id, andreport_type. Usereport_idwith the report status and download endpoints.- The event is sent for every report of the account that finishes successfully, including reports requested in Cint Exchange and by other API clients. It doesn't identify who requested the report.
- A failed report sends no event; check the report status endpoint.
ChangedCorrected report IDs and statuses
6 November 2026
Endpoints: Generate Report, Get report requests, Report Request Status
report_id: a ULID, for example01HY3NF37B6J2ABPA3H49C92YZ. The generate report response and the list of report requests documented it as a UUID.status: a new report isprocessing. The report status endpoint then returns the pipeline's run state, for exampleRUNNING, thenSUCCESS, orFAILED,TIMEDOUT, orCANCELEDif the job doesn't finish successfully. It returnsfailed, in lower case, when the pipeline couldn't start the job or read its state. The documentation listedpending/emailedandCOMPLETED/IN PROGRESS.email_recipients: removed from the report generation guide. This version's generate report request doesn't have the field.
The API itself has not changed.
ChangedProfile condition text is optional
2 November 2026
Affected fields: text, text_translated
Endpoints: Replace all profiles for a target group with provided profiles, Get profiles, Get profile, Create a profile, and the other Manage Profiling endpoints that return profile conditions
text and text_translated on a profile condition are now documented as optional. They are left out when the condition has no display text, which is common on range and postal code conditions and on the profiles of an interlocked profile. id is always returned. The API itself has not changed.
ChangedCorrected interlocked profile condition contracts
2 November 2026
Endpoints: Generate interlocked profile from provided profiles, Create a target group in draft status, Retrieve a draft target group, Update a target group in draft status
The conditions of interlocked profiles are now documented as the API returns and accepts them. The API itself has not changed: if you built against the previous documentation, check your integration against these points.
conditions.objectisselection_conditions_details_template,range_conditions_details_template, orzip_conditions_details_template, and sets the shape of every condition indata. The previous documentation listed the values without the_templatesuffix.- Each condition carries only the fields of its type:
optionfor selection,minandmaxfor range, andzip_codesandallow_all_zipfor postal code conditions. The previous documentation required all of them on every condition. id,text, andtext_translatedare optional. Generating an interlocked profile returnsid, andtextandtext_translatedwhen the condition has display text. The target group endpoints returntextonly.
ChangedCorrected target group contracts
2 November 2026
Endpoints: Create a target group in draft status, Retrieve a draft target group, Update a target group in draft status, Retrieve a target group's changelog
The fields below are now documented as the API returns and accepts them. The API itself has not changed: if you built against the previous documentation, check your integration against these points.
- Grouped quotas:
indexesrefers to conditions by zero-based position, so each index is0or greater, and a group lists at least two indexes. The previous documentation required each index to be2or greater. - Changelog:
old_valueandnew_valueon atest_url_changeentry can benull.
ChangedCorrected the feasibility error code format
2 November 2026
Affected fields: errors[].code on 422 responses
Endpoints: Provides Target Group feasibility on draft mode, Provides target group feasibility on draft mode (Deprecated)
The errors[].code field is now documented as the API returns it. The API itself has not changed. Profile validation codes end in a number, such as profile_validation_error_015, so a code is lowercase letters and digits separated by underscores. The previous documentation allowed letters and underscores only. If you validate error codes against the documented pattern, update it.
ChangedRecontact studies require respondent IDs before launch
12 October 2026
We identified and fixed an issue that allowed some users to launch a Recontact Study without providing Respondent IDs.
AddedDefault flag on the account allocation template response
8 October 2026
Affected fields: is_default
Endpoints: Retrieve an allocation template by ID
The response now includes is_default, which is true when the template is the account's default allocation template and false otherwise.
AddedRequest ID header on webhook deliveries
7 October 2026
Every webhook request now carries a Cint-Request-Id header that identifies that request.
Key details:
- Every delivery attempt, including a retry, carries a new ID, so don't use it to de-duplicate events.
- Log the header for every request your endpoint receives. If you contact Cint support about a webhook request, for example one that failed signature verification, include its
Cint-Request-Idso support can find the exact delivery attempt.
Version: Added to all available versions.
ChangedCorrected job and exclusion group response fields
5 October 2026
Affected fields: failure_reason, created_fielding_run_id, job_trace_id, update_date
Endpoints: Retrieve a launch from draft job, Retrieve a schedule from draft job, Get an upload-by-file job status, Retrieve the status of a Recontact upload-by-file job, Get information on a remove all Recontact opportunities job, Retrieve an exclusion group by ID, List exclusion groups for an account, List the exclusion groups of a target group
These fields are now documented as the API returns them. The API itself has not changed: if you built against the previous documentation, check your integration against these points.
- Fielding run jobs:
failure_reasonis always returned. It isnullwhile the job is processing or after it completes, and an object when it fails.created_fielding_run_idandjob_trace_idare omitted when they have no value, not returned asnull. - Recontact jobs:
job_trace_idis omitted unless the jobstatusisFailed. - Exclusion groups:
update_dateis omitted for an exclusion group that has never been updated.
AddedAllocation changes added to the target-group-updated webhook
1 October 2026
Twelve allocations_* change objects added to the target-group-updated webhook. Four report changes to a target group's open exchange and private exchange allocations, and eight report changes to the allocation groups within them.
Group-scoped change objects carry allocation_group_id, which identifies the allocation group the new value applies to. Without it, a change such as a group maximum percentage moving to 91 gives no indication of which group it belongs to.
Existing change objects are unaffected. If your endpoint ignores object values it does not recognize, no change is needed.
Webhooks: Understanding webhook event notifications
Version: Added to releases from 2025-05-27 onwards.
AddedExclude respondents by activity status
9 September 2026
You can now target specific respondent statuses in respondent activity exclusions using the new optional respondent_statuses array on each exclusion item. Previously, the activity-history check matched only a Complete status (the concurrent-participation check for live target groups is unchanged).
List the same project or target group more than once, pairing each entry with a distinct set of statuses and its own duration, to apply different exclusion windows to different statuses. When omitted, respondent_statuses defaults to ["Complete"], so existing configurations are unaffected. Supported statuses: Complete, Terminate, SecurityFailure, OverQuota, FinancialTerm, PreClientSurveyProcess.
Statuses other than Complete require your account to have access to this feature.
Endpoints: Set respondent activity exclusions, Retrieve respondent activity exclusions, Create target group, Update target group, Get target group
AddedOptional gzip compression for webhook deliveries
7 September 2026
You can now receive webhook request bodies compressed with gzip. Set compression to gzip when you create or update a webhook, and every delivery for that webhook carries the Content-Encoding: gzip header. Content-Type stays application/json, because compression changes only how the body is encoded, not its media type.
Key details:
- Compression is not enabled by default. Omit the field, or set it to
null, to keep receiving uncompressed bodies. - The
Cint-Signatureheader still covers the uncompressed JSON, so your existing verification code keeps working. - Updating a webhook replaces it, so an update that omits
compressiondisables it. Include the field in every update to keep compression on.
Endpoints: Create webhook, Update webhook
Version: Added to all available versions.
ChangedCorrected Update quotas response codes
19 August 2026
Endpoints: Update quotas
- Fixed the success status code — updating quotas returns
200. - Documented the
422response returned for invalid requests. - Documented the
404response returned when a project or target group does not exist.
ChangedCorrected Intelligent Calendar contracts
3 August 2026
Endpoints: Suggest time range, Suggest days
The documented Intelligent Calendar contracts now match the API.
- The time range response returns
suggested_startandsuggested_end, notstartandend. This applies to every API version — the service has returned these names since June 2024, so clients readingstart/endreceivedundefined. localeis required on suggest time range.days,start, andendare optional on suggest time range: provide eitherdaysalone, or bothstartandend. Combining them returns400.incidence_ratebounds are exclusive: values of exactly0or1are rejected.pricerequires bothvalueandcurrency_code.valuemust be a positive decimal greater than 0 encoded as a string, andcurrency_codeacceptsUSDonly.- Error examples on both endpoints now show the
objectvalues the service emits:bad_request,unauthorized, andinternal_server_error. - A
401on these endpoints means either that credentials are missing or invalid, or that the caller doesn't have the role required for the operation. Both cases returnobject: unauthorized.
ChangedAutomatic deduplication of zip codes
1 July 2026
Endpoints: Validate profiles, create or update draft target group, Apply profiles, Create profile, Update profile conditions
Submitting duplicate zip codes no longer causes the request to fail. The API now automatically removes duplicate zip codes in the request before validating or saving, but rejects duplicates in selection or range conditions.
Addedsupplier_id added to target-group-updated webhook change objects
16 June 2026
supplier_id added to supplier-scoped change objects on the target-group-updated webhook. The field identifies the supplier a change applies to and is currently included on private_exchange_cpi_change change objects.
Webhooks: Understanding webhook event notifications
Version: Added to releases from 2025-05-27 onwards.
Addedrespondent_update_date added to the sessions data webhook
3 June 2026
respondent_update_date added to the sessions data webhook payload (com.cint.session.updated). This timestamp records the most recent update to a respondent session record and is updated on every status change, including reconciliations. It differs from respondent_last_date_change, which is set once when the session first reaches a terminal status and does not change thereafter.
Webhooks: Understanding webhook event notifications
Version: Added to releases from 2025-05-27 onwards.
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.
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.
ChangedCorrected reconciliation, fielding assistant, and glossary guidance
9 November 2026
Several guides now match how the Cint Exchange behaves. The API itself has not changed.
Updated guides:
- Glossary: the fielding assistant entry maps its four API modules to the five Cint Exchange UI features. New entries for prescreens, completed target groups, and relaunch. Filling strategy notes the UI default: automated, with Prevent overfilling on. The reconciliation policy entry states the key rules instead of linking to a page that requires sign-in.
- Understanding the fielding assistant: Prevent overfilling is described as converting the filling goal into equivalent prescreen quotas, and the recommendation to enable it notes the exception for buyers who manage their own click balancing.
- Reconciling respondents: states the reconciliation policy's key rules (a reason code for every reversal, and a deadline of end of day Central Time on the 25th of the month after the session was completed) instead of linking to a page that requires sign-in.
- Exclude respondents within the same project: respondents who completed another target group in the project are excluded, not every respondent who entered one.
ChangedCorrected the webhook envelope id, source, and time
6 November 2026
The webhooks deep dive now documents three CloudEvents envelope fields as they're delivered:
idis a ULID. It was documented as a UUID. It identifies the event sent to the webhook: each webhook gets its ownidfor an event, it's theidthat the events history endpoint returns, and a retry carries the sameid, so you can use it to de-duplicate deliveries. Until 9 November 2026, a retry carried a newid.sourceidentifies the webhook subscription, ashttps://api.cint.com/v1/accounts/{account_id}/webhooks/{webhook_id}. It was documented ashttps://api.cint.com.timeis when the delivery was sent, not when the event occurred. It has up to 9 fractional-second digits and the number of digits varies, so don't parse it with a fixed-precision format. The examples showed 3 digits.
Apart from the id on retries, the webhooks themselves have not changed.
AddedWebhook request ID
7 October 2026
The webhooks deep dive now documents the Cint-Request-Id header.
Updated deep dives:
- Understanding webhooks: covers what the
Cint-Request-Idheader identifies, why it changes on every retry, and when to include it in a support request.
ChangedCorrected target-group-updated webhook change objects
7 October 2026
The webhooks deep dive now lists three previously undocumented change objects delivered by the target-group-updated webhook. The webhook already delivered these change objects. The API itself has not changed.
Updated guides:
- Understanding webhook event notifications —
pricing_rate_card_boost_cpi_change,target_group_customer_reference_number_change, anduser_requested_cpi_changeadded to the list of demand changelog change objects.
ChangedExclude respondents by activity status
9 September 2026
The respondent activity history check is no longer limited to completes. You can now configure which respondent statuses each exclusion targets, and apply different exclusion windows to different statuses.
Updated guides:
- Setting up respondent activity exclusions covers how to configure
respondent_statuses, the supported statuses, and the account access requirement. - How respondent activity exclusions work explains how per-status rules are evaluated independently.
AddedWebhook gzip compression
7 September 2026
Webhook deliveries can now be gzip compressed. The webhooks deep dive covers how to turn it on and what changes for your endpoint.
Updated deep dives:
- Understanding webhooks — New Compression section covering the
compressionfield, theContent-Encoding: gzipheader, signature verification against the uncompressed JSON, how a toggle applies to queued deliveries, and what to expect from payload sizes.
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.