MunchReach API overview

MunchReach exposes a REST API at /api/public/v1. Everything you can do on the dashboard for campaigns, sequence steps, contacts, replies and analytics has an API equivalent, and every request is scoped to one workspace.

When you need this

Use the API when you want to push contacts from your own system, create and launch campaigns programmatically, or pull performance data into a reporting tool.

Base URL

All endpoints live under https://munchreach.com/api/public/v1.

What the API covers

• GET /me — verify a key and see its workspace, scopes and rate limit
• Campaigns — list, create, retrieve, update, delete, launch/pause/resume/stop, stats
• Sequences — list, add, update and delete steps on a campaign
• Contacts — list, create or update, retrieve, update, delete, bulk operations, CSV export
• Mailboxes — list and retrieve connected mailboxes (read only)
• Replies — list inbound replies with sentiment classification
• Analytics — workspace-level performance
• Webhooks — create, list, update and delete endpoints, plus delivery history

Your first call

Create a key in Settings → API Keys, then verify it:

curl -H "Authorization: Bearer $MUNCHREACH_API_KEY" https://munchreach.com/api/public/v1/me

A 200 response returns the workspace name and the scopes the key carries. A 401 means the key is wrong, revoked or expired.

Important notes

• There is no workspace parameter anywhere in the API. A key resolves to exactly one workspace, so you cannot read another workspace's data with it.
• The full interactive reference, with request and response examples in cURL, JavaScript and Python, lives on the API reference page.

Common problems

• 404 on every path — you left /api/public/v1 off the URL.
• 401 on `/me` — the key is not being sent as Authorization: Bearer ….