How to integrate with Cobre

This is the client view of a Cobre API integration: what you do, what you wait for, and who to ask. Your Key Account Manager (KAM) is the commercial point of contact. They tell you the next step for your account — including how the Solution Design is produced and who supports you during implementation.

Use the Development Toolkit throughout: Create a Solution Design with AI, Build with AI, Generate Code with MCP, and Explore API Workflow Examples.

The journey

Pre-sales → Integration → Certification / Go-live → Support

Stage	What it means for you
Pre-sales	Commercial and technical conversations. You are not yet building against Cobre’s integration environment.
Integration	You confirm the design you will implement, then your engineers build and test.
Certification / Go-live	You demonstrate the integration and Cobre certifies it before production.
Support	Your KAM remains the contact. They introduce any additional Cobre contacts if that applies to your account.

1. Pre-sales

Work with your commercial contact and KAM. Typical activities: product fit, proposal, due diligence, and contract discussion.

Your KAM shares the documentation your technical team needs — including this Development Toolkit. You do not need production credentials yet. Use Get started to learn the platform model (Accounts, Counterparties, Money Movements).

2. When integration can start

Integration work starts only when all of the following are true. Your KAM confirms them — you do not need to track Cobre’s internal systems.

Your commercial agreement is at or past signature.

A Key Account Manager is assigned to your account.

Cobre has opened an API onboarding for you.

Until then, you stay in pre-sales. If your engineers are ready earlier, tell your KAM — they will say when credentials and environments are available.

3. Integration

Follow the sequence your KAM sets. A typical path looks like this:

Align with your KAM

Description: Depending on the size of your expected operation volumes and integration complexity, your KAM may decide to schedule a technical kickoff with your team and a Cobre Solution Engineer.

What to expect after the action: You know who your Cobre contacts are and what happens next.

Confirm the design you will implement

Description: You can also draft a Solution Design with your own team using Create a Solution Design with AI. Cobre will document a Solution Design only when the KAM decides to bring a Solution Engineer.

What to expect after the action: Your Product and Engineering teams have a design to implement against.

Start development

Description: Tell your KAM that development has started. Request QA credentials when you need them. See Build in QA.

If the KAM identified that the size of your expected operation volumes and integration complexity is significant, your team may have access to a Cobre Integration Engineer support via Slack or WhatsApp groups (or email).

What to expect after the action: Your team implements the agreed flows in Cobre’s test environment where those products are available.

4. Build in QA

Request QA credentials (client_id and client_secret) from your KAM. Authenticate as in Authentication. The QA base domain is https://api.qa.cobre.co.

Not every product is available in QA. Check General Testing for the current matrix (for example, some Mexico and Cross Border surfaces are not in QA). Use Testing Cases for recommended happy and failure paths.

While you build:

Need	Use
Platform model	Get started and Quick Start
Live OpenAPI spec in your IDE	Build with AI
API sequences	Explore API Workflow Examples
Scaffolding from the spec	Generate Code with MCP
Docs-grounded Q&A	Connect Cobre's Documentation to AI
API and product change notices	Managing API and Product Changes

Refresh the Cobre Docs MCP in the same chat before you generate code or a Solution Design. Do not implement from memory or from an old spec cache.

5. Certification and go-live

When the integration is ready to operate, request certification through your KAM (or your Integration Engineer point of contact). Full detail: Certification Process.

Before the session:

Review the Questionnaire and be able to answer it.

Prepare a live demo of the flows you implemented.

The session covers the questionnaire and a live demonstration against Cobre’s QA or production environment, depending on availability. Cobre then issues a certification report (score, feedback, issues, recommendations). You go live only after the integration is certified, or after you close any required adjustments.

6. After go-live

Your KAM and the Integration Engineer remain the contacts for production issues, new products, and API-change communication. Your KAM will tell you if additional Cobre contacts stay involved after go-live.

Watch Managing API and Product Changes so your implementation stays aligned with the published spec.

Create a Solution Design with AI — generate a Markdown design from live Cobre documentation

Build with AI — connect the Cobre Docs MCP in your IDE

Explore API Workflow Examples — interactive walkthroughs of Cobre API sequences

Generate Code with MCP — prompts to scaffold code from the live spec

Get started — Accounts, Counterparties, and Money Movements

Authentication — obtain and reuse API tokens

General Testing — QA environment and what you can test

Certification Process — questionnaire, live demo, and report

Managing API and Product Changes — how Cobre notifies you when APIs change

How to integrate with Cobre

The journey#

1. Pre-sales#

2. When integration can start#

3. Integration#

4. Build in QA#

5. Certification and go-live#

6. After go-live#

Related guides#

The journey

1. Pre-sales

2. When integration can start

3. Integration

4. Build in QA

5. Certification and go-live

6. After go-live

Related guides