API Reference
Obert REST API — authenticate with a User API key and call generated endpoints by domain.
The Obert REST API manages the same workspace data as the web app — leads, lists, campaigns, signals, inbox, and more.
Authentication
Create a User API key under Settings → Integrations → User API Keys. See API keys.
Send the key on every request:
Authorization: Bearer <your-api-key>Treat keys like passwords. Revoke unused keys from the integrations page.
Base URL
https://api.obert.ioExplore endpoints
Browse auto-generated operations by domain:
- Accounts — company accounts and scoring
- Leads — leads and enrichment
- Lists — lead and account lists
- Campaigns — campaigns and workflows
- Analytics — dashboards, reports, and live queries
- Signals — signal definitions
- Signal Runs — signal execution history
- LinkedIn Accounts — connected LinkedIn accounts and limits
- Posts — LinkedIn post data
- Contacts — 1st-degree connections
- Inbox — messaging
- Imports — bulk imports
- Jobs — async job status
- Snippets — reusable message snippets
- Tracker — nurture / warmup tracking
- Tenant — workspace and members
OpenAPI drives these pages. Regenerate locally with npm run generate:api when the backend schema changes.
Common patterns
Async jobs — Many writes return a job ID. Poll job endpoints (see Jobs) until completion.
Enrichment — Reverse email lookup is documented in Enrichment (POST /api/enrichment/reverse-email-lookups).
MCP — AI clients can use the Obert MCP server with OAuth instead of hand-rolling REST calls.
Rate limits
API keys share workspace rate limits with the product. On 429 responses, back off and retry.