ClinchPad API

Name: ClinchPad API API
Brand: ClinchPad API
Availability: InStock

★ Only Publicly Available OpenAPI DocumentCRMDeal Pipelinebasic63 EndpointsREST

For Agents

Manage leads, contacts, organizations, pipelines, stages, and notes in the ClinchPad sales CRM. 63 endpoints with HTTP Basic auth.

Connect the ClinchPad API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the ClinchPad API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.

Install Jentic One Beta (Self-Hosted)

Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh

Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
jentic register       # connects your agent to your Jentic One instance

Jentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.

Capabilities

What an agent can do with ClinchPad API API.

Create new leads and move them between pipeline stages

Attach contacts to leads and update contact field values

Manage organizations and their custom field values

List and configure pipelines along with their ordered stages

GET STARTED

Start building with ClinchPad API API

Explore with Jentic

View OpenAPI Document

Jentic publishes the only available OpenAPI document for ClinchPad API, keeping it validated and agent-ready.

Jentic publishes the only available OpenAPI specification for ClinchPad API, keeping it validated and agent-ready. ClinchPad is a sales CRM organized around leads moving through pipeline stages. The API exposes 63 endpoints covering leads, contacts, organizations, pipelines and their stages, products, notes, todos, activities, custom fields, lead sources, and users. Authentication is HTTP Basic with the literal username api-key and the user's API key as the password. The surface fits classic sales-pipeline workflows: importing leads, advancing them through stages, attaching contacts and notes, and reporting on activity.

Use Cases

Patterns agents use ClinchPad API API for, with concrete tasks.

★ Inbound Lead Capture

Marketing forms and chat widgets need to push new prospects into the sales CRM the moment they convert. POST /leads creates the lead with the source attached, POST /contacts adds the person, and a single PUT against the lead's stage field places the lead in the right pipeline column. The whole capture-to-CRM flow is three calls.

POST /leads with name, source_id, and pipeline_id, then POST /contacts and link via PUT /leads/:lead_id/contacts/:contact_id

Pipeline Stage Automation

Sales operations teams enforce stage rules (for example a lead must have a contact and a deal value before reaching Negotiation). GET /pipelines/:pipeline_id/stages returns the ordered stages, and the lead update endpoints move the lead forward only when fields are populated. This keeps the pipeline data clean for forecasting.

GET /pipelines/:pipeline_id/stages, then PUT /leads/:lead_id with the next stage_id only after verifying required fields are populated

Activity and Note Logging

Account executives need every call, email, and meeting to be visible on the lead record without manual data entry. The notes, todos, and activities endpoints take the AE's structured event and attach it to the right lead so the next person on the deal sees full context.

POST a note to /leads/:lead_id/notes with the call summary and create a follow-up todo on the same lead

Agent-Driven Lead Triage

An AI agent triaging inbound leads uses Jentic to query ClinchPad for similar past deals, attach context to the new lead, and assign the right user. Jentic returns the lead, contact, and user endpoints with their schemas, the agent loads them, executes with HTTP Basic auth, and updates the lead in one chained workflow.

Use Jentic to search for create lead and assign user, load the schemas, execute POST /leads then PUT to update assigned_user_id

Key Endpoints

63 endpoints — jentic publishes the only available openapi specification for clinchpad api, keeping it validated and agent-ready.

METHOD

PATH

DESCRIPTION

POST

/leads

Create a new lead

GET

/leads

List leads

PUT

/leads/:lead_id

Update a lead (including stage)

POST

/contacts

Create a contact

PUT

/leads/:lead_id/contacts/:contact_id

Link a contact to a lead

GET

/pipelines/:pipeline_id/stages

List ordered stages of a pipeline

POST

/organizations

Create an organization

PUT

/contacts/:contact_id/fields/:field_id

Update a custom field value on a contact

POST

/leads

Create a new lead

GET

/leads

List leads

PUT

/leads/:lead_id

Update a lead (including stage)

POST

/contacts

Create a contact

PUT

/leads/:lead_id/contacts/:contact_id

Link a contact to a lead

GET

Why though Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

ClinchPad's HTTP Basic credential (api-key as username, the user's API key as password) is stored encrypted in the Jentic MAXsystem vault. The agent never sees the raw key; Jentic assembles the Basic header at execution time.

Intent-based discovery

Agents search by intent (for example create a lead in clinchpad) and Jentic returns POST /leads with its request schema, including pipeline_id and source_id structure, so the agent calls it correctly without reading docs.

Time to first call

Direct integration: 1-2 days to wire HTTP Basic auth and walk through 63 endpoints across leads, contacts, organizations, and pipelines. Through Jentic: under an hour to first lead created and staged.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Complementary

Climbo

Reputation management; pairs with ClinchPad to send review requests after a deal closes

Use Climbo to send a review-request campaign after a ClinchPad lead reaches the Won stage

Alternative

NLM Clinical Tables

Different domain reference data API; included as catalog neighbor only

Not a real CRM alternative; agents should not select this for sales pipeline work

Complementary

Clip

Payments API; pairs with CRM when a closed deal needs to be invoiced

Use Clip to collect payment for a deal that ClinchPad has marked as Won

FAQs

Specific to using ClinchPad API API through Jentic.

Why is there no official OpenAPI spec for ClinchPad API?

ClinchPad does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call ClinchPad API via structured tooling. It is validated against the live API and kept up to date. Get started at https://app.jentic.com/sign-up.

What authentication does the ClinchPad API use?

ClinchPad uses HTTP Basic authentication. Use the literal string api-key as the username and your ClinchPad API key as the password on every request to https://www.clinchpad.com/api/v1. Through Jentic the API key is held encrypted in the MAXsystem vault and assembled into the Basic header at execution time.

Can I move a lead between pipeline stages with this API?

Yes. GET /pipelines/:pipeline_id/stages returns the ordered stage_ids for a pipeline, and PUT /leads/:lead_id with the new stage_id moves the lead. There is no separate move endpoint; updating the lead with the target stage handles the transition.

What are the rate limits for the ClinchPad API?

The OpenAPI spec does not publish numeric rate limits. Apply exponential backoff on 429 or 5xx responses. For bulk lead imports, batch requests and add jitter rather than firing dozens of parallel POST /leads calls.

How do I create and stage a lead through Jentic?

Run pip install jentic, search Jentic for create clinchpad lead, load the schema for POST /leads, and execute with the lead payload. Jentic injects the api-key Basic header from the vault. Get started at https://app.jentic.com/sign-up.

Does ClinchPad support custom fields on leads, contacts, and organizations?

Yes. The fields endpoints (PUT /contacts/:contact_id/fields/:field_id and PUT /organizations/:organization_id/fields/:field_id) update custom field values on the corresponding records. Field definitions themselves are managed in the ClinchPad workspace.