LeadArc Inbox API

Read and act on cold email replies in the Master Inbox. No browser session needed.

Read

Filter leads, read a whole conversation, pull notes, tasks and meetings.

Act

Tag a lead, mark it read or responded, book or disqualify it, add notes and tasks.

Report

Funnel, per rep, per campaign and daily numbers.

In one minute

bash

export LEADARC_API_KEY=lak_live_k7m2p9qh_...

# 1. What can this key reach?
curl -sS https://api.leadarc.io/v1/me -H "Authorization: Bearer $LEADARC_API_KEY"

# 2. Today's interested replies in one workspace
curl -sS "https://api.leadarc.io/v1/workspaces/airpay/leads?status=interested&limit=25" \
  -H "Authorization: Bearer $LEADARC_API_KEY"

The basics

Base URL	`https://api.leadarc.io/v1`
Auth	`Authorization: Bearer lak_live_...`
Endpoints	41
Scopes	17, named `resource:action`
Pagination	Cursor only. `limit` defaults to 50, max 200
Rate limits	120/min read, 60/min write, 10/min upstream, 4 at once
Timestamps	ISO 8601 UTC with a `Z`. Days are `YYYY-MM-DD`
CORS	None. Server to server only, so keys stay out of browsers

Machine readable

llms.txt

The whole API as plain text. One fetch, paste into a model.

openapi.json

OpenAPI 3.1 for every endpoint, for tool generation.

Every page also has a .md twin. Use the card at the top of any page.

GET /v1/capabilities returns the same facts live from the server.

What v1 cannot do

Send email. Nothing here reaches a prospect's inbox. That is v2.
Spend money. No enrichment, no paid provider calls.
Change EmailBison. Campaigns and tags are read only.
Delete anything. Deletes are soft. No row is removed.
Make keys. No endpoint mints a key, so a leaked key cannot widen itself.
Run in a browser. There are no CORS headers.

Get a key

A signed-in human makes one in the app under Settings, Developers, API keys. Then read Getting started.