Uses the user-provided information to create a compliance report.
The criteria property in the request body must be populated using the fields returned by the GET /criteria/{type} endpoint.
Ensure you first retrieve the criteria for the desired report type using the GET /criteria/{type} endpoint before making this request.
Optional. The team to work in, using a team id from List Teams. If left out, the default team is used. Records created in a team can only be seen by sending that team's id. A team id that doesn't exist, or a team being deleted, is rejected with 404 Team Not Found.
Request body containing the report type, file name, and criteria details for creating a compliance report.
The criteria field must adhere to the schema provided by the GET /criteria/{type} endpoint.
The criteria used to create the report, as name and value pairs. The names and values depend on the report type and must match the criteria returned by GET /reports/criteria/{type}. For example, amlAlert accepts fromDate, toDate, hitDecisions and hasHits, and audit accepts fromDate, toDate and audit filters. Values can be strings, booleans or arrays, as described by each criterion's type.
- Sandbox serverhttps://connect.sandbox.creditsafe.com/v1/compliance/kyc-protect/reports
- Production serverhttps://connect.creditsafe.com/v1/compliance/kyc-protect/reports
curl -i -X POST \
https://connect.sandbox.creditsafe.com/v1/compliance/kyc-protect/reports \
-H 'Authorization: Bearer <YOUR_JWT_HERE>' \
-H 'Content-Type: application/json' \
-H 'X-Team-Id: 6b78aed4-9ba6-441b-80b9-df9bea3b7c97' \
-d '{
"type": "amlScreen",
"fileName": "openapi-test-screen-144102",
"criteria": {
"searchId": "511a38c1-2016-420d-84bb-0873be8d4d2b",
"hitIds": [
"2f25fb51-f976-4b7a-b885-8f2ac4cd4716"
]
}
}'Success
Current processing status of the report. Indicates the lifecycle stage, such as:
- submitted: The report request has been submitted.
- queued: The report is waiting to be processed.
- inProgress: The report is currently being generated.
- completed: The report has been successfully created.
- failed: The report generation encountered an error.
Type of the report, determining the data and format of the results. Supported values:
- amlAlert: Report for Anti-Money Laundering alerts.
- audit: Report for audit-related compliance checks.
- profile: Report for a profile.
- amlScreen: Report for an AML screening search and its hits.
- monitorSearch: Report for AML monitored searches.
The unique identifier of the user who initiated the creation of the report.
The timestamp of the last modification made to the report, if applicable.
The criteria used to generate the report, reflecting the filters and parameters applied during its creation.
The structure of the criteria object depends on the report type, and matches the criteria returned by GET /reports/criteria/{type}. Values can be strings, booleans or arrays.
The expiration timestamp for the report, after which it may no longer be accessible.
{ "id": "6d0104f1-fa7f-466a-933b-7a22200241ab", "fileName": "openapi-test-screen-144102", "status": "submitted", "type": "amlScreen", "createdAt": "2026-11-03T14:41:02.218Z", "createdById": 100000001, "createdByUser": "Jane Smith", "criteria": { "searchId": "511a38c1-2016-420d-84bb-0873be8d4d2b", "hitIds": [ … ] }, "expiresAt": null, "correlationId": "4ee1fa95-024e-4d02-aad6-3ab9b77d3b4e" }