API and data access
How to get your numbers out of OutboundManager: CSV, HubSpot properties, Slack and email reports, and the read-only JSON endpoints behind the dashboards.
For: RevOps and developers
There are two different things people mean by "API" here. The keys you paste in to connect your tools are covered in API keys by tool. This page is about getting data out.
Important: OutboundManager does not issue API keys or tokens of its own today. There is no public, versioned API for server-to-server use. What exists is listed below. If you need a token-based API, tell us what you would build with it.
Ways to get data out
| You want | Use |
|---|---|
| Attribution inside your CRM reports | HubSpot write-back: four deal properties. See Attribution and HubSpot write-back. |
| A weekly summary in a channel or inbox | The weekly report by Slack webhook or email. See The weekly report. |
| Enrichment results in a spreadsheet | The CSV download on each enrichment run. |
| An answer to a one-off question | Ask, which answers from the report data and links to the report. |
| The dashboard numbers as JSON | The read-only endpoints below, from a signed-in browser session. |
Read-only JSON endpoints
The dashboards read their numbers from a small set of JSON endpoints. They return exactly what the screens show, with the same access rules. You can call them from a browser tab where you are signed in.
| Endpoint | Returns |
|---|---|
GET /api/metrics/overview | The Overview tiles, daily series and excluded-reply counts |
GET /api/metrics/reps | The rep scorecard |
GET /api/metrics/rep?id=<rep id> | One rep's page |
GET /api/metrics/campaigns | The campaigns table. Optional tool and channel (email or linkedin) |
GET /api/metrics/campaign?id=<campaign id> | One campaign's page |
GET /api/metrics/replies | The reply list. Optional class, rep, assignee, campaign, page |
GET /api/metrics/attribution | A summary of how many deals are attributed, and by which rule. Managers and admins |
Period
Add from and to as dates in the workspace time zone, both inclusive. With neither, the period is this week.
GET /api/metrics/reps?from=2026-10-05&to=2026-10-11Response
Every response is JSON and starts with the same fields, followed by the data for that endpoint:
{
"workspaceId": "ws_...",
"timezone": "America/New_York",
"from": "2026-10-05",
"to": "2026-10-11",
"days": 7,
"scope": "team",
...
}scope is team for a manager or admin and rep for a rep, whose results only cover their own data.
Errors
| Status | Meaning |
|---|---|
| 401 | Not signed in |
| 403 | Your role may not use this endpoint |
| 404 | Unknown endpoint or id. A rep asking for another rep's data also gets 404, as if it did not exist |
What to expect from these endpoints
- They are authenticated by your signed-in session cookie only. There is no key to put in a script or a server.
- They are read-only. Nothing can be changed through them.
- They are not versioned. Field names can change when a screen changes. Do not build something critical on them without talking to us first.
- The ids in the query string are the ones in the page addresses, for example the last part of
/reps/<id>.
A full export
There is no self-serve full export yet. To ask for a copy of your workspace data, contact us from an admin's address. The Privacy policy explains your data rights.
Something unclear or out of date? Tell us and we will fix this page.