canonical: https://jentic.com/apis/clarkup.com/clarkup

# Clarkup API

Jentic publishes the only available OpenAPI specification for Clarkup API, keeping it validated and agent-ready. Clarkup is a sales pipeline tool focused on inbound lead capture, and its public API exposes a focused surface for OAuth authorization and lead creation. The spec covers the OAuth 2.0 authorization and token exchange endpoints plus a single Zapier-style lead creation endpoint that drops a new lead into a Clarkup pipeline. It is intentionally minimal and aimed at integration partners that need to push leads in, not browse or enrich the existing pipeline.

## For AI agents

Push new leads into a Clarkup sales pipeline after completing OAuth 2.0 authorization, suitable for inbound capture forms, chat handoff, or AI agent intake bots.

## Scope

Does not handle deal updates, contact enrichment, or pipeline reporting - use for inbound lead creation through OAuth-authorised workspaces only.

## Capabilities

- Initiate OAuth 2.0 authorization for a Clarkup workspace via /oauth/authorize
- Exchange an authorization code for an access token via /oauth/token
- Create a new lead in the connected Clarkup pipeline via /zapier/create-lead
- Identify the authorising user from the OAuth grant before posting leads
- Pass lead context such as name, email, and source so the lead lands in the correct stage

## Use cases

### Inbound Lead Capture from Web Forms

Forward web form submissions, webinar registrations, and chatbot handoffs straight into Clarkup as new leads after a one-time OAuth connection. The /zapier/create-lead endpoint accepts the lead payload directly so partner integrations skip building a heavier sync layer.

Example prompt: Call /zapier/create-lead with the contact's name, email, source, and notes after a form submission, using the cached OAuth bearer token.

### Partner OAuth Onboarding

Run a one-click OAuth connection flow that lets a Clarkup user authorise a third-party app to push leads into their workspace. The /oauth/authorize redirect kicks off consent and /oauth/token exchanges the resulting code for a refresh-capable access token.

Example prompt: Redirect the user to /oauth/authorize with client_id, scope, and redirect_uri, then post to /oauth/token with the returned code to obtain an access token.

### AI Agent Lead Intake via Jentic

An AI agent that runs an outbound prospecting bot or an inbound concierge can drop qualified leads into Clarkup at the moment of capture by searching Jentic for the lead-creation operation and executing it. Jentic securely stores the OAuth bearer token so the agent never holds the secret directly.

Example prompt: Use the Jentic search query 'create a sales lead' to find /zapier/create-lead and execute with the qualified contact details from the conversation.

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| GET | /oauth/authorize | Start the OAuth 2.0 authorization flow |
| POST | /oauth/token | Exchange an authorization code for an access token |
| POST | /zapier/create-lead | Create a new lead in the connected Clarkup workspace |

## Key resources

- **OAuth** — Authorisation and token exchange endpoints for connecting a Clarkup workspace
- **Leads** — Single endpoint for creating a new lead in the connected workspace

## Why Jentic

- **Setup:** Wiring Clarkup by hand means running its OAuth flow to mint a bearer token, then keeping that token attached to every call against app.clarkup.com. Through Jentic you install once, import Clarkup from the API Directory, store the token once, and your agent calls it.
- **Permission scoping:** You choose which Clarkup operations the agent may call, so you can limit it to the operations it needs, such as creating a lead, and leave the token and authorize operations out of the allowed set unless you add them.
- **Credential handling:** Your Clarkup token is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context.
- **Discovery method:** Agents search Jentic by intent such as 'create a lead in Clarkup', and Jentic returns the matching operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Pipedrive** — Sales CRM with full pipeline, deal, and activity APIs
- **Close** — Sales CRM with rich lead, opportunity, and outreach APIs
- **HubSpot** — Marketing automation and CRM platform

## FAQ

### Why is there no official OpenAPI spec for Clarkup API?

Clarkup does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call Clarkup API via structured tooling. It is validated against the live API and kept up to date. Get started with Jentic One, the self-hosted execution layer.

### What authentication does the Clarkup API use?

The API uses OAuth 2.0 authorization code flow via /oauth/authorize and /oauth/token, returning a bearer token used on /zapier/create-lead. Through Jentic the bearer token is stored in the encrypted vault and the agent receives only a scoped execution context.

### Can I create a Clarkup lead with the API?

Yes. POST to /zapier/create-lead with the lead payload after completing the OAuth flow. This is the only lead-mutation endpoint in the public spec, designed for inbound capture rather than full pipeline management.

### Can I read existing Clarkup leads or pipeline stages with this API?

No. The public spec only exposes lead creation and OAuth endpoints. To read or move existing leads, use the Clarkup app directly until additional endpoints are released.

### How do I push a lead into Clarkup through Jentic?

Search Jentic for 'create a sales lead', load the schema for /zapier/create-lead, and execute with the lead details. The Python SDK uses await client.search, await client.load, await client.execute.

### How do I complete the OAuth handshake?

Send the user to /oauth/authorize with client_id, scope, and redirect_uri. After consent Clarkup redirects with a code that you exchange at /oauth/token to receive an access token.

### Can I limit what my agent is allowed to do with the Clarkup API?

Yes. Because you run Jentic One yourself, you decide which Clarkup operations the agent may call, and your own rules are what allow or block each one. You can restrict the agent to the /zapier/create-lead operation for inbound lead creation while leaving the /oauth/authorize and /oauth/token operations out of the allowed set unless you add them. The stored token is injected only at execution time, so the agent acts only within the operations you have permitted.