Pipeline CRM

    Get Started with the Pipeline CRM API

    The Pipeline CRM API lets you read and write your CRM data from your own apps, scripts, and workflows.

    Before you start: Your account needs API access switched on. An admin turns it on under Settings > API, and will need a technical contact email to complete it.

    What You Can Do

    • Access and manage people, companies, deals, and activities.
    • Create and update records from external applications.
    • Search and filter data across every list endpoint — see Filter API Results.
    • Export filtered data as CSV for deals, people, companies, notes, and calendar entries.
    • Capture leads from your website with Web-to-Leads.

    Three Ways to Authenticate

    Any of these credentials works with any endpoint. Pick the one that suits what you're building.

    Credential

    Best for

    How to get it

    API token

    Anything new you build. Named, scoped, individually revocable, with an expiry you choose.

    Create and Manage API Tokens

    JWT

    Existing integrations already built on it.

    Unchanged — see the API docs

    API key

    Existing integrations and Web-to-Leads.

    Settings > API > API Keys

    We recommend API tokens for any new implementation.

    Find Your API Key or W2LID

    The legacy API key still works exactly as it does today. To retrieve it:

    1. Click Settings in the lower-left corner.
    2. Select the API tab.
    3. Open API Keys to retrieve the API key or W2LID for a user.
    4. Open API Integrations to generate an App Key for a connected application.

    You only see keys for users at or below your own role level, and on your own team. Users with the Executive role see keys for everyone. See Understand User Roles and Permissions.

    Read the Documentation

    The full reference lives at app.pipelinecrm.com/api/docs and covers 142 endpoints. It includes:

    • An interactive console — try any endpoint against your own account by pasting in a token. The token is never stored and never passes through a third party.
    • A filtering chapter and an interactive filter builder that writes the query string, full URL, and sample code for you.
    • Rate limits in writing, including the response headers that report your remaining budget.
    • A downloadable OpenAPI spec and Postman collection.
    • A data model diagram and an llms.txt file so AI tools can read the API cleanly.

    The documentation is now a single reference page. Older deep links to individual doc pages will land you on the main reference rather than the exact section.

    Ask a Question About the API

    A floating Ask about the API button sits in the bottom-right corner of the reference page. It answers questions about endpoints, parameters, filter conditions, response fields, status codes, pagination, and authentication — grounded in the published reference, with copyable code blocks.

    It's available to signed-in users, allows up to 30 questions per hour, and doesn't save conversations. Answers are generated from the reference and can be wrong, so check the reference before relying on them.

    Rate Limits

    API tokens allow 10 requests per second per user, shared across all of that user's tokens. Successful responses report your remaining budget in the response headers. Going over returns an HTTP 429 — pause briefly and retry, reading your budget from a recent successful response.

    Verify Your Webhooks

    If you send data out through an automation's Call an API action, you can have Pipeline CRM sign each delivery so your receiver can confirm it's authentic. See Verify Webhooks with Request Signing.

    Need help? Contact support at customercare@pipelinecrm.com.