Your first Qampi API call
Use the Qampi API to bring campaign workflows, leads, and outcomes into your own product. This quick start verifies your account connection in one request.
Before you begin
API access is available on Pro and Business plans. Create a key in Settings → API keys; Qampi only shows the full key once.
Create an API key
Give each integration its own key so you can revoke it without affecting another workflow.
Make a request
Pass the key in the Authorization header. Start with GET /me to confirm your account and LinkedIn session are ready.
curl https://api.qampi.com/api/public/v1/me \
-H "Authorization: Bearer qampi_live_…"Read the response
A successful response includes your plan, onboarding state, and LinkedIn connection health. Use this check before starting a campaign from an external workflow.
{
"id": "usr_1",
"email": "you@company.com",
"tier": "PRO",
"onboardingComplete": true,
"linkedin": { "connected": true, "health": "HEALTHY" }
}Rate limits
Each API key can make up to 120 requests per minute. When you exceed the limit, the API returns 429 RATE_LIMITED. Keep retries exponential and respect the reset time when it is included in the response.
Error codes
Every error includes a stable error code and an actionable message. Common setup responses are ONBOARDING_INCOMPLETE, UPGRADE_REQUIRED, LINKEDIN_SESSION_EXPIRED, EMAIL_ACCOUNT_REQUIRED, and QUOTA_EXCEEDED.
Campaigns
Campaigns are template-based. List templates first, then create a campaign from a chosen template. A launch checks your LinkedIn session, connected email account when needed, quotas, and active-campaign status.
Leads
Import one lead or up to 100 leads in one request. Qampi deduplicates LinkedIn URLs and preserves enrichment. You can update tags and notes, while campaign status remains managed by Qampi.
Search & enrich
Search for LinkedIn people with keywords and filters, or find a work email using a person’s name and company. These calls use your plan’s search and email-finder credits.
Webhooks
Register a webhook to receive lead lifecycle events. Save the signing secret returned during creation and verify every X-Qampi-Signature against the raw request body.
Use Qampi through MCP
The Qampi MCP server connects Codex, Claude Code, and Cursor to the same API. It starts read-only; write tools are unavailable until you deliberately set QAMPI_MODE=full.
[mcp_servers.qampi]
command = "npx"
args = ["-y", "@qampi/mcp-server"]
env = { QAMPI_API_KEY = "qampi_live_…" }Connect from Codex
Add the MCP configuration above to ~/.codex/config.toml, replace the API key, and restart Codex. Qampi tools will appear in your available tool list.
Connect from Claude Code
Add the same server command and QAMPI_API_KEY environment variable to your Claude Code MCP settings, then start a new session to load the server.
Connect from Cursor
Open Cursor settings, add an MCP server using npx -y @qampi/mcp-server, supply QAMPI_API_KEY, then reload the editor window.
Account reference
Use the account endpoints to identify the current workspace and see remaining invite, search, and email credits. The /me endpoint works before onboarding is complete to help diagnose setup.
Templates reference
Templates expose their supported channels, required plan, required account connections, campaign duration, and the content fields you can override.
Campaigns reference
Create a campaign from a template, inspect its funnel, enroll leads, and launch it after the Qampi preflight checks pass.
Leads reference
List, import, inspect, and tag leads. Lead statuses are calculated by the campaign engine and cannot be set through the API.
Webhooks reference
List registered destinations, create a new signed subscription, send a test event, or remove a webhook no longer in use.