Cobre’s Evidence Requests API provides a secure, auditable, and structured mechanism to request, collect, and review supporting documentation and information required for compliance, fraud prevention, and risk management processes.

This cross-feature service integrates with core platform resources such as Money Movements, Counterparties, and Destinations, enabling Cobre and clients to collaborate efficiently when additional evidence is required to satisfy regulatory or internal controls.

Evidence Requests follow a clear lifecycle driven by notifications, secure uploads, and structured submissions, ensuring transparency, traceability, and operational reliability.

Creating Evidence Requests (Conceptual Overview)

Evidence Requests are initiated by Cobre and delivered to clients through Notifications & Subscriptions.
Clients do not create evidence requests directly, but instead react to them by submitting the required documents and information.

To receive Evidence Requests, clients must subscribe to the event:

evidence-request.ask

Once subscribed, clients will receive a webhook every time a new evidence request is created.

Evidence Requests Lifecycle

Notification
A webhook is sent to the client with the evidence_request_id, deadline, context, and required evidence types.

Evidence Submission
Clients submit the requested evidence through:

Documents → Uploaded using signed URLs

Information → Submitted as structured JSON payloads

Completion
Once the submission is completed (or the deadline expires), the request transitions to completed.

Clients can submit evidence only once per evidence request. Subsequent submissions are not allowed.

Evidence Request Notification

Clients receive evidence requests through the Notifications API when subscribed to evidence-request.ask.

Notification Schema

{
  "id": "ev_1234567890",
  "event_key": "evidence-request.ask",
  "event_type": "EvidenceRequest",
  "timestamp": "2024-06-01T12:00:00.000Z",
  "content": {
    "evidence_request_id": "evr_01923801823",
    "evidence_request_context": {
      "counterparty_id": "cp_456"
    },
    "evidence_request_description": "Please provide the required documents and information.",
    "evidence_requested": {
      "documents": ["doc_funds"],
      "information": ["information_counterparty_id"]
    }
  }
}

Evidence Request Context

The evidence_request_context object identifies what triggered the evidence request and helps clients correlate it with their internal systems.

Context Fields

Field	Description
`counterparty_id`	Counterparty associated with the request
`mm_id`	Money Movement that triggered the request
`destination_id`	Destination resource identifier
`destination_type`	Type of destination identifier (e.g., RFC, NIT)
`destination_number`	Destination identification number
`destination_fullname`	Full name of the destination
`destination_account_number`	Destination account number
`destination_providers_id`	Provider-specific destination identifier

Not all fields are present in every request. The context depends on what triggered the evidence request.

Evidence Types Catalog

Evidence can be requested in two formats: Documents and Information.

Document Types

Information Types

Document Type	Expected Evidence
`doc_funds`	Proof of funds and justification for unusual money movements
`official_identification_copy`	Government-issued ID (passport, driver’s license, etc.)
`identification_and_address_copy`	Government-issued ID plus proof of address

Information Schema

When the requested information type is information_counterparty_id, the following structured payload must be submitted:

{
  "data": {
    "full_name": "string",
    "country_of_birth": "string",
    "date_of_birth": "yyyy-mm-dd",
    "address": {
      "city": "string",
      "country": "string",
      "address_line_1": "string",
      "number": "string",
      "zip_code": "string"
    },
    "document": {
      "id_nationality": "string",
      "id_type": "string",
      "id_number": "string"
    },
    "occupation": "string",
    "phone_number": "string",
    "email": "string",
    "gender": "string"
  }
}

Actions performed on Evidence Requests

🔍 Retrieval

📄 Get by ID

⬆️ Upload Documents

⬇️ Download Documents

📨 Submit Information

Description: Search and retrieve evidence requests using filters such as status, creation date, and update date.

What to expect after the action:
A paginated list of Evidence Request objects including status, deadlines, and required evidence.

📘 Learn more: 🔗 Obtain all Evidence Requests

Evidence Request Object

An Evidence Request represents a single compliance or risk investigation case.

Key Attributes

Field	Description
`id`	Unique identifier of the evidence request
`reference_id`	External reference (case, transaction, process)
`expiration_date`	Deadline to submit evidence
`status`	`initiated`, `pending_information`, `completed`
`evidence_requested`	Documents and information required
`evidence_documents`	Uploaded documents
`evidence_information`	Submitted structured information
`created_at`	Creation timestamp
`updated_at`	Last update timestamp

How to Get Started

Subscribe to evidence request notifications

Subscribe to the evidence-request.ask event using the Notifications & Subscriptions API.

Receive and parse the webhook

Capture the evidence_request_id, context, and required evidence from the webhook payload.

Upload requested documents

Generate upload URLs and securely upload the requested documents.

Submit required information

Provide structured information using the submission endpoint.

Monitor request completion

Retrieve the evidence request to verify its final status.

What to expect after using this API

Regulatory compliance readiness

Respond efficiently to compliance and fraud-related evidence requests.

Secure evidence handling

Ensure sensitive information is transmitted using signed URLs and structured schemas.

Operational transparency

Maintain a full audit trail of evidence requests and submissions.

Cross-feature traceability

Link evidence requests back to money movements, counterparties, and destinations.

Evidence API

Creating Evidence Requests (Conceptual Overview)#

Evidence Requests Lifecycle#

Evidence Request Notification#

Notification Schema#

Evidence Request Context#

Context Fields#

Evidence Types Catalog#

Information Schema#

Actions performed on Evidence Requests#

Evidence Request Object#

Key Attributes#

How to Get Started#

What to expect after using this API#

Creating Evidence Requests (Conceptual Overview)

Evidence Requests Lifecycle

Evidence Request Notification

Notification Schema

Evidence Request Context

Context Fields

Evidence Types Catalog

Information Schema

Actions performed on Evidence Requests

Evidence Request Object

Key Attributes

How to Get Started

What to expect after using this API