Connect anything to PipeCrush.
A REST API for pushing leads in, syncing contacts, and wiring PipeCrush into the tools you already run. Authenticate with a single key — no OAuth flow to build, no SDK to install.
$ curl https://www.pipecrush.tech/api/v1/contacts \
-H "Authorization: Bearer pc_live_your_key_here"
{
"data": [
{
"id": "cnt_8fq2k1",
"email": "jane@acme.com",
"first_name": "Jane",
"last_name": "Doe",
"customer_id": "cus_4m9p2x"
}
],
"next_cursor": null
}How it works
Three steps between you and your first request.
Create a key
In PipeCrush, go to Settings → API Keys and click Create key. Name it after the integration it's for, then copy it — it's shown only once.
Call the API
Send the key as a bearer token on every request to https://www.pipecrush.tech/api/v1. JSON in, JSON out.
Build your integration
Push leads from your website, sync contacts on a schedule, or create a task when something changes in your own systems.
Six resources
All six ship together, and every one follows the same shape: list, create, fetch, and update.
Contacts
List, create, fetch, and update the people linked to a company record.
Leads
Capture new leads from your own forms, backend, or third-party tools.
Customers
Manage the company records your contacts and deals attach to.
Tasks
Create a follow-up automatically when something changes in your own systems.
Tickets
Open and track support tickets from outside PipeCrush.
Deals
Create and update deals against a pipeline and stage you choose.
Push a lead in one request
Send a lead from your own website backend with a single request.
curl -X POST https://www.pipecrush.tech/api/v1/leads \
-H "Authorization: Bearer pc_live_your_key_here" \
-H "Content-Type: application/json" \
-d '{ "email": "jane@example.com", "first_name": "Jane", "company": "Acme" }'Unknown response fields are always safe to ignore — we only ever add to v1. Breaking changes ship as a new version path, /api/v2.
Prefer codegen? Pull the full spec from GET /api/v1/openapi.json — an OpenAPI 3.1 document with stable, tool-shaped operation IDs, live now.
Built for production access
An API key is a real credential to real customer data. It's handled like one.
Scoped to your workspace
A key can only see what its creator can see. An admin's key sees the whole organization; anyone else's is scoped the same way their account is.
Revoke it anytime
Rotating credentials or lost a key? Revoke it from Settings and traffic stops immediately — no support ticket required.
Encrypted in transit
Every request runs over TLS. Keys travel in an Authorization header, never in a URL or a query string.
Server-side only
Treat an API key like a password: keep it in your backend. Never ship it in browser code, a mobile app, or a public repo.
Predictable rate limits
Every response includes an X-RateLimit-Remaining header. If you go over, you'll get a 429 with a Retry-After header telling you exactly how long to wait.
- Per minute
- 120
- Max page size
- 100
| HTTP | Code | Meaning |
|---|---|---|
| 401 | invalid_api_key | Missing, malformed, or revoked key |
| 403 | permission_denied | Key lacks write access for this call |
| 404 | not_found | No such record in your workspace |
| 422 | validation_failed | Bad input — see errors[] for fields |
| 429 | rate_limited | Slow down — retry after Retry-After seconds |
| 500 | internal_error | Our fault — safe to retry with backoff |
Coming soon
MCP server
Connect an AI agent directly to your PipeCrush data using the Model Context Protocol.
Frequently asked questions
How do I get a PipeCrush API key?
Go to Settings → API Keys in PipeCrush (admin role required), click Create key, and name it after the integration you're building. Copy the key immediately — it's shown only once.
What can I do with the PipeCrush API today?
All six resources are live: contacts, leads, customers, tasks, tickets, and deals. Each supports list, create, fetch, and update.
How is the API authenticated?
Send your API key as a bearer token on every request: Authorization: Bearer pc_live_your_key_here. There is no OAuth flow to build — one key, sent on every call.
What are the rate limits?
120 requests per minute per key. If you exceed it you'll get a 429 response with a Retry-After header telling you how long to wait.
Is there an OpenAPI spec or an MCP server?
A machine-readable OpenAPI 3.1 spec is live at GET /api/v1/openapi.json, with stable, tool-shaped operationIds for codegen and AI tooling. An MCP server for connecting agents directly to your data is coming soon.
Ready to build?
Create a free PipeCrush account, then generate a key from Settings → API Keys.