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 Fielding API

Create, update and obtain Target Group Fielding runs and Fielding Assistant assignments. This is critical for launching, scheduling and completing Target Groups.

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

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

This API exposes 12 operations across 11 paths, and defines 28 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.

12 operations 11 paths 28 schemas 4 GET7 POST1 PUT

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 Fielding 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 12

Across 11 paths, the API surfaces 12 operations — 4 GET, 7 POST, 1 PUT. Each is listed below with its method, path, parameters, and response codes.

Fielding 12

Create, update and obtain Target Group Fielding runs and Fielding Assistant assignments. This is critical for launching, scheduling and completing Target Groups.

POST
/demand/accounts/{account_id}/projects/{project_id}/target-groups/{target_group_id}/fielding-run-jobs/launch-from-draft
Job to launch a draft target group
create_launch_fielding_run_from_draft_job 5 params body → 201400401403429500
GET
/demand/accounts/{account_id}/projects/{project_id}/target-groups/{target_group_id}/fielding-run-jobs/launch-from-draft/{job_id}
Retrieves a "launch from draft" job status
get_launch_fielding_run_from_draft_job 5 params → 200400401403404429500
POST
/demand/accounts/{account_id}/projects/{project_id}/target-groups/{target_group_id}/fielding-run-jobs/schedule-from-draft
Schedules a draft target group to go live
create_schedule_fielding_run_from_draft_job 5 params body → 201400401403429500
GET
/demand/accounts/{account_id}/projects/{project_id}/target-groups/{target_group_id}/fielding-run-jobs/schedule-from-draft/{job_id}
Retrieves a "schedule from draft" job status
get_schedule_fielding_run_from_draft_job 5 params → 200400401403404429500
GET
/demand/accounts/{account_id}/projects/{project_id}/target-groups/{target_group_id}/fielding-runs
Lists the fielding runs for a target group
get_fielding_runs_by_target_group_id 4 params → 200400401403404429500
GET
/demand/accounts/{account_id}/projects/{project_id}/target-groups/{target_group_id}/fielding-runs/{fielding_run_id}
Retrieves a fielding run
get_fielding_run 5 params → 200400401403404429500
PUT
/demand/accounts/{account_id}/projects/{project_id}/target-groups/{target_group_id}/fielding-runs/{fielding_run_id}
Updates a fielding run
update_fielding_run 6 params body → 202400401403404412422429
POST
/demand/accounts/{account_id}/projects/{project_id}/target-groups/{target_group_id}/fielding-runs/{fielding_run_id}/complete
Completes a fielding run
complete_fielding_run 6 params body → 204400401403404412422429
POST
/demand/accounts/{account_id}/projects/{project_id}/target-groups/{target_group_id}/fielding-runs/{fielding_run_id}/launch-now
Launches fielding run immediately
launch_now_fielding_run 6 params body → 200400401403404412422429
POST
/demand/accounts/{account_id}/projects/{project_id}/target-groups/{target_group_id}/fielding-runs/{fielding_run_id}/pause
Pauses a fielding run
pause_fielding_run 6 params body → 204400401403404412422429
POST
/demand/accounts/{account_id}/projects/{project_id}/target-groups/{target_group_id}/fielding-runs/{fielding_run_id}/relaunch
Relaunches a fielding run
relaunch_fielding_run 6 params body → 204400401403404412422429
POST
/demand/accounts/{account_id}/projects/{project_id}/target-groups/{target_group_id}/fielding-runs/{fielding_run_id}/resume
Resumes a fielding run
resume_fielding_run 6 params body → 204400401403404412422429

Schemas 28

The contract defines 28 schemas that model the data the API accepts and returns. The most detailed are GetLaunchFieldingRunFromDraftJobResponse (7 properties), GetScheduleFieldingRunFromDraftJobResponse (7 properties), FieldingRunItem (7 properties), Error (4 properties). Each schema is shown below with its type and property counts.

LaunchNowFieldingRunResponse
object
Response for launching a fielding run now.
2 properties 2 required
UpdateFieldingRunRequest
object
Request for updating a fielding run for a given target group id.
2 properties 2 required
CreateLaunchFieldingRunFromDraftJobRequest
object
Request body for creating a launch fielding run from draft job.
1 property 1 required
ETag
string
The ETag header provides a unique identifier that represents the current version state of a particular resource.
ProjectID
string
The character string representing a unique project ID (ULID format).
FieldingRunID
string
A unique identifier for the fielding run.
FieldingRunItem
object
The version of the fielding run. This value is used in the If-Match header for optimistic locking when making updates.
7 properties 7 required
JobID
string
The character string representing a unique job ID.
GetFieldingRunResponse
GetScheduleFieldingRunFromDraftJobResponse
object
Schedule fielding run from draft job details.
7 properties 4 required
FieldingRunJobStatus
string
The status of an asynchronous job. Processing indicates the job is still running. Completed or Failed are terminal states.
InvalidParam
object
Describes a single invalid parameter in a request.
2 properties 2 required
FieldingRunJobFailureReason
object
Provides details about why a fielding run job failed.
3 properties 2 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.
UpdateFieldingRunResponse
object
Response for updating a fielding run for a given target group id.
1 property 1 required
Traceparent
string
The traceparent header carries essential trace context information. This includes the trace ID and parent span ID as defined by the W3C trace context specifica…
GetListFieldingRunsResponse
object
List of fielding runs for a given target group id.
2 properties 2 required
GetLaunchFieldingRunFromDraftJobResponse
object
Launch fielding run from draft job 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.
Tracestate
string
The tracestate header provides additional contextual information to the traceparent header. This enriches the tracing context and offers more fine-grained cont…
CreateScheduleFieldingRunFromDraftJobRequest
object
Request body for creating a schedule fielding run from draft job.
2 properties 2 required
Error
object
The standard error object returned for all failed API requests.
4 properties 2 required
FieldingRunJobFailureReasonDetail
object
Provides granular, machine-readable details for a single validation error.
3 properties
IdempotencyKey
string
A shallow unique ID used as part of the deduplication mechanism for mutable operations. We suggest using UUIDv4 or another random string with sufficient entrop…
FieldingRunStatus
string
The current status of a fielding run. A scheduled run will become live at its start time. A live run is actively collecting completes.
TooManyRequestsProblemDetails
object
The error payload returned when the rate limit has been exceeded.
2 properties 2 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

cint-fielding-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 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
Cint Profiling Helper API
Where this information came from

This is an independent, third-party profile of Cint Fielding 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.