How to reconcile respondents for invoice adjustments

This guide explains how to submit respondent IDs to Cint for reconciliation, allowing you to remove poor-quality target group completes from your invoicing.

After a target group's completion, you may identify respondents whose answers are of poor quality (e.g., fraudulent, inconsistent, or nonsensical). By reconciling these respondents, you can ensure they are not included in your invoice. Additionally, your reconciliation data helps Cint to continuously improve supplier quality and enhance automated security tools across the exchange.

Prerequisites:

• You have access to the Cint API.
• You've completed a target group and identified specific respondent IDs (RIDs) that you want to reconcile because of poor quality.
  • You can generate a report to get a CSV file containing all RIDs available for reconciliation.
• You've reviewed and understood Cint's reconciliation policy.
• You have the necessary roles assigned to your client.

---

Steps to reconcile respondents

Step 1: Prepare your reconciliation CSV file

Organize RIDs and their reason codes into CSV format.

In the example below, we reconcile three RIDs. We positively reconcile two RIDs (convert them from a terminated status to a complete status so they are counted towards the total quota in a target group), while the last RID has a reason code to terminate the RID (this removes the RID from counting towards the total quota for the target group).

30AA2CCB-9668-4E56-94E2-C0E279EFAE6B, 11
923AC8C0-BD60-4236-AAB2-B6E723402400, 11
8445F477-77D3-47F9-A900-CEAEA885BF0E, 932

You can submit up to 100,000 RIDs in a single submission.

info

You can call the reconciliation reason codes endpoint to find Cint's accepted reason codes.

Step 2: Submit your reconciliation request

• Call the submit reconciliations endpoint, include your CSV values in the request body. The name query parameter is required.

Example request to submit a CSV file:

curl -L \
  -X POST \
  'https://api.cint.com/v1/demand/accounts/{account_id}/reconciliations?name=myFileForReconciliation' \
  -H 'Content-Type: text/csv' \
  -H 'Accept: application/json' \
  -H 'Authorization: Bearer <YOUR_JWT_TOKEN>' \
  --data-binary "30AA2CCB-9668-4E56-94E2-C0E279EFAE6B, 11\n923AC8C0-BD60-4236-AAB2-B6E723402400, 11\n8445F477-77D3-47F9-A900-CEAEA885BF0E, 932"

• The API returns a request_id and the name of the CSV data.

{
  "name": "myFileForReconciliation.csv",
  "request_id": "01F8K8P3Z5KNYR5H0GQZAYGQJ9"
}

Step 3: Verify the status of a specific reconciliation request

Check the processing status of a particular reconciliation submission using its unique request ID.

• Call the retrieve a reconciliation request by ID endpoint.
• Parameter: Use the request_id returned from the submission response.

Example request to check status:

GET https://api.cint.com/v1/demand/accounts/{account_id}/reconciliations/01F8K8P3Z5KNYR5H0GQZAYGQJ9

The response will contain a summary of information for the submission:

{
  "request_id": "01F8K8P3Z5KNYR5H0GQZAYGQJ9",
  "name": "myFileForReconciliation.csv",
  "status": "complete",
  "submitted_at": "2026-01-01T23:00:00.000Z",
  "submitter_las_id": "4325c214c-2d72-7as2-b498-d6345342ff10b0",
  "submitted_count": 3,
  "expired_count": 0,
  "invalid_count": 0,
  "positive_reversed_count": 2,
  "negative_reversed_count": 1
}

---

Troubleshooting common issues

• Reconciliation deadline: Remember the trailing-month deadline. RIDs achieved in a given month can only be reconciled until the 25th of the following month. Submissions for RIDs past this deadline will be rejected.
• CSV file formatting: Separate your RID and reason code with commas.
• File size exceeded: If your CSV file exceeds 100,000 IDs, split it into multiple smaller CSV groups and submit each separately.
• RID or reason code not found/invalid: Verify that the RID you are trying to reconcile is correct, belongs to one of your completes, and falls within the reconciliation policy guidelines. Verify you are using correct reason codes.