How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Cint Recontacts API

Create, update, list and delete recontacts for a target group. Recontacts allow only specific respondents to enter your survey and are part of a larger workflow that needs specific configurations across other endpoints.

Cint Recontacts API is one of 25 APIs that Cint publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Recontacts. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, an API reference, and a getting-started guide.

This API exposes 10 operations across 9 paths, and defines 22 schemas. It is described by OpenAPI 3.2.0, at version 2025-12-18.

Requests are made against a single base URL, https://api.cint.com/v1.

10 operations 9 paths 22 schemas 7 GET3 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
2025-12-18
Base URL
https://api.cint.com/v1
Authentication
HTTP Bearer, API Key
Resource Areas
1

Authentication & Security 2

Cint Recontacts API declares 2 security schemes for authenticating requests. It accepts HTTP bearer tokens (JWT) (BearerAuth). An API key is passed in the header as Authorization (ApiKeyAuth). By default, every request must be authenticated.

  • BearerAuth — Bearer token used for authentication and authorization. See [Authentication Process](https://developer.cint.com/en/guidesauthentication-process) documentation…
  • ApiKeyAuth — API Key Authentication

Paths & Operations 10

Across 9 paths, the API surfaces 10 operations — 7 GET, 3 POST. Each is listed below with its method, path, parameters, and response codes.

Recontacts 10

Create, update, list and delete recontacts for a target group. Recontacts allow only specific respondents to enter your survey and are part of a larger workflow that needs specifi…

POST
/demand/accounts/{account_id}/projects/{project_id}/target-groups/{target_group_id}/recontacts/jobs/remove-all-rsids
Create a job to remove all recontact respondent IDs
create_all_recontact_rsids_removal_job 4 params → 201400401403404409500
GET
/demand/accounts/{account_id}/projects/{project_id}/target-groups/{target_group_id}/recontacts/jobs/remove-all-rsids/{job_id}
Get information on a remove all Recontact opportunities job
recontacts_remove_all_rsids_job_status 5 params → 200400401403404500
POST
/demand/accounts/{account_id}/projects/{project_id}/target-groups/{target_group_id}/recontacts/jobs/upload-rsids-by-file
Create a job to upload respondent IDs by file
recontact_create_upload_rsids_by_file_job 4 params body → 201400401403404409413415
GET
/demand/accounts/{account_id}/projects/{project_id}/target-groups/{target_group_id}/recontacts/jobs/upload-rsids-by-file/{job_id}
Get an upload-by-file job status
get_recontacts_rsids_upload_file_job_status 5 params → 200400401403404500
POST
/demand/accounts/{account_id}/projects/{project_id}/target-groups/{target_group_id}/recontacts/jobs/upload-respondents-by-file
Create a job to upload Recontact opportunities by file
recontact_create_upload_respondents_by_file_job 5 params body → 201400401403404409413415
GET
/demand/accounts/{account_id}/projects/{project_id}/target-groups/{target_group_id}/recontacts/jobs/upload-respondents-by-file
List Recontact upload-by-file jobs
recontact_list_upload_respondents_by_file_jobs 6 params → 200400401403404500
GET
/demand/accounts/{account_id}/projects/{project_id}/target-groups/{target_group_id}/recontacts/jobs/upload-respondents-by-file/{job_id}
Retrieve the status of a Recontact upload-by-file job
get_recontact_upload_respondents_by_file_job 5 params → 200400401403404500
GET
/demand/accounts/{account_id}/projects/{project_id}/target-groups/{target_group_id}/recontacts/jobs/upload-respondents-by-file/{job_id}/download
Download the file associated with a Recontact upload job
recontact_download_job_file 5 params → 200400401403404500
GET
/demand/accounts/{account_id}/projects/{project_id}/target-groups/{target_group_id}/recontacts/overview
Get recontact overview for a target group
get_recontacts_overview 4 params → 200400401403404500
GET
/demand/accounts/{account_id}/projects/{project_id}/target-groups/{target_group_id}/recontacts/rsids
List recontact respondent IDs
get_target_group_rsid_recontact_list 7 params → 200400401403404500

Schemas 22

The contract defines 22 schemas that model the data the API accepts and returns. The most detailed are GetRecontactRsidsUpdateJobResponse (8 properties), GetRecontactRemoveAllRsidsJobStatusResponse (7 properties), GetUploadByFileJobResponse (5 properties), Error (4 properties). Each schema is shown below with its type and property counts.

GetRecontactRsidsUpdateJobResponse
object
The response payload containing the status and details of a recontact job.
8 properties 4 required
CreateRecontactUploadRespondentsByFileJobResponse
object
The response payload containing the jobid for a newly created Recontact upload-by-file job.
1 property 1 required
ProjectID
string
The character string representing a unique project ID (ULID format).
GetRecontactUploadRespondentsByFileJobResponse
The response payload containing the status and details of a Recontact upload-by-file job.
RecontactJobPartialSuccessReason
object
The reason for the partial success of a job.
1 property 1 required
JobID
string
The character string representing a unique job ID.
GetUploadByFileJobsPaginatedResponse
object
Paginated response containing upload recontacts by file jobs.
2 properties 1 required
GetTargetGroupRecontactsOverviewResponse
object
The response payload containing the recontact overview for a target group.
1 property 1 required
InvalidParam
object
Describes a single invalid parameter in a request.
2 properties 2 required
CreateRecontactUploadRsidsByFileJobResponse
object
The response payload containing the jobid for the newly created file upload job.
1 property 1 required
TargetGroupID
string
A unique identifier for the target group, in ULID format.
AccountID
integer
The account's unique identifier.
UserID
string
A unique identifier for the user.
RecontactUploadJobEntityType
string
Indicates the respondent entity type. Use RSID or RESPONDENTID for Respondent IDs, and RID or RESPONSEID for Response IDs.
RecontactsRespondentIDListResponse
object
The response payload for a paginated list of respondent IDs.
3 properties
RecontactJobFailureReason
object
The reason for the failure of a job.
2 properties 2 required
GetUploadByFileJobResponse
object
Summary details for an upload recontacts by file job.
5 properties 5 required
GetRecontactRemoveAllRsidsJobStatusResponse
object
Recontacts Remove All RSIDs job status details.
7 properties 4 required
JobTraceId
string
The trace ID from the creation job request. Only present when the job status is 'Failed'. The trace ID as defined by the W3C trace context specification.
Error
object
The standard error object returned for all failed API requests.
4 properties 2 required
CreateRecontactsJobResponse
object
The response payload containing thejobidfor a newly created recontact job.
1 property 1 required
RecontactJobStatus
string
The status of an async Recontact update job.

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

cint-recontacts-api-openapi.yml Raw ↑

Other APIs Cint publishes across the network.

Cint Accounts API
Cint Allocation Templates Admin API
Cint Definitions API
Cint Exclusive Endpoints API
Cint Feasibility API
Cint Fielding API
Cint Fielding Assistant API
Cint Fielding (Batch) API
Cint Fulfillment API
Cint Intelligent Calendar API
Cint Manage Profiles for Launched Target Groups API
Cint Notifications Webhooks API
Where this information came from

This is an independent, third-party profile of Cint Recontacts API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.