API & MCP — Overview
DURUM.ai exposes a read-only API and an MCP server so you can access your own data (ad spend, attribution, funnel, contacts, call scorecards, ICP scores, CAPI health…) from your own tools: a BI dashboard, a script, or your AI assistant (Claude, Cursor…).
The principle
You get your results (the numbers). DURUM's optimization engine, AI models, prompts and internal costs are never exposed.
What you can access
| Domain | Examples |
|---|---|
| Dashboard / KPIs | spend, revenue, leads, bookings, sales, ROAS, CAC |
| Ads | spend & performance by campaign |
| Attribution | multi-touch attribution per ad |
| Events | leads, bookings, sales, payments, refunds |
| Sales | sales KPIs, reps, pipeline, no-show |
| Finance | P&L, revenue (internal margins not exposed) |
| Funnel | stages, conversion by source/campaign |
| Contacts & Calls | contacts, call scorecards |
| ICP · CAPI · Health · Goals | ICP criteria, conversion health, data scores |
Two ways to use it
- REST API — call
https://app.durum.ai/api/v1/…with your key. → Authentication · API Reference - MCP server — plug DURUM into your AI assistant and ask in natural language. → Set up MCP
Security & isolation
- Each API key is bound to your account only. You can never access another client's data.
- Access is granular: a key can only read the scopes you grant it.
- Everything is read-only. No data can be modified through the API.
- Every request is logged.
Personal data (Law 25 / GDPR)
The API can return your prospects' data (emails, call transcripts). You are responsible for using it in compliance with applicable regulations.