Skip to main content
Version: 2025-12-18

Changelog

2025-12-18

New Cint Exchange Demand API version 2025-12-18​

Issued 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 and 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 “name” field 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. Please see the JSON example below.
  • Property fields have been renamed to improve clarity:
    • ”filling_goal” → ”completes_goal”
    • ”quota_percentage” → ”completes_goal_percentage”
    • ”quota_nominal” → “completes_goal”
    • ”index” → ”condition”
    • ”indexes” → ”conditions”
    • ”ungrouped” → ”target”
    • ”grouped” → “target”
    • ”interlocked_profiles” → now specified by the ENUM value blended within ”profiles”: []
  • Endpoints have been renamed to match the new and updated features:
    • /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 the launched target groups:

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,
           "quota_nominal": 492,
           "completes": 0,
           "prescreens": 0
         }
       },
       {
         "id": "01JY5V67FAY2N5TB8TSK6HWM2G",
         "text": "Mujer",
         "text_translated": "Female",
         "conditions": [
           {
             "object": "selection",
             "question_id": 43,
             "option": "2"
           }
         ],
         "quota": {
           "name": "SF-BirthGender-Quota-2",
           "completes_goal_percentage": 50.79,
           "completes_goal": 508,
           "quota_nominal": 508,
           "completes": 0,
           "prescreens": 0
         }
       }
     ]
   }
 ]

Feasibility​

Removed feasibility features:​

  • Updated the feasibility endpoint to simplify calls by removing the requirement for project_id
    • POST https://api.cint.com/v1/demand/accounts/{account_id}/projects/{project_id}/target-groups/calculate-feasibility
    • The new endpoint is: POST https://api.cint.com/v1/demand/accounts/{account_id}/target-groups/calculate-feasibility
  • The ”supplier_ids” : [] within the “allocations”: object matches its usage across other endpoints.

General improvements​

  • Updated error messages clarify what went wrong to increase clarity.

Additional changes and improvements​

  • Human-readable-id has been changed to the snake-case standard human_readable_id.
    • GET https://api.cint.com/v1/demand/accounts/{account_id}/projects/{project_id}
  • The target group performance endpoint now has its currency format updated to match every other endpoint.
    • ”completes_cost” {“value”: “2.7352”, “currency_code” : “USD”, “currency_scale” : NULL}
  • “client_cpi” has changed to “client_cost_per_interview_note” to improve clarity that the value is referring to a note and not the actual CPI of the target group.
  • “pricing_model” and ”type” Enum value of “ratecard” has changed to “rate_card” to match the snake-case standard.
    • 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}/overview
    • https://api.cint.com/v1/demand/accounts/{account_id}/business-units/{business_unit_id}/generate-price-prediction

Deprecated endpoints and attributes​

  • Removed the feasibility endpoint, which was marked as deprecated in API version 2025-05-27

    • POST https://api.cint.com/v1/demand/accounts/{account_id}/projects/{project_id}/target-groups/calculate-feasibility

  • Removed Exclusion endpoints, which were marked as deprecated in API version 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

  • Removed ‘Download Report’, which was marked as deprecated from 2025-05-27

    • GET https://api.cint.com/v1/demand/accounts/{account_id}/reports/download)

  • Removed purchase_order_number attribute, which was marked as deprecated in API version 2025-05-27

    • GET https://api.cint.com/v1/demand/accounts/{account_id}/projects
    • POST https://api.cint.com/v1/demand/accounts/{account_id}/projects
    • GET https://api.cint.com/v1/demand/accounts/{account_id}/projects/{project_id}
    • PUT https://api.cint.com/v1/demand/accounts/{account_id}/projects/{project_id}
    • GET https://api.cint.com/v1/demand/accounts/{account_id}/projects/{project_id}/overview

  • Removed the “name” attribute, which was marked as deprecated in API version 2025-05-27

    • https://api.cint.com/v1/demand/accounts/{account_id}/projects/{project_id}/target-groups
    • https://api.cint.com/v1/demand/accounts/{account_id}/projects/{project_id}/target-groups

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.