Copper CRM API

Name: Copper CRM API API
Brand: Copper CRM API
Availability: InStock

★ Only Publicly Available OpenAPI DocumentCRMDeal PipelineapiKey59 EndpointsREST

For Agents

Manage people, companies, leads, opportunities and pipelines in Copper CRM, including custom fields, related items and webhook subscriptions.

Quickstart

Get started with Copper CRM API in minutes using your preferred integration method.

# Add to your MCP client config (Claude Desktop, Cursor, Windsurf)
{
  "jentic": {
    "url": "https://api.jentic.com/mcp",
    "auth": "oauth"
  }
}

# Then ask your agent:
"create or update a person in Copper CRM"

# → Jentic returns the GET /events tool with parameter schema, agent executes.

Capabilities

What an agent can do with Copper CRM API API.

Create or update a person record and attach related companies and tags

Move an opportunity through pipeline stages and record loss reasons when it closes lost

Search people or companies with filtered POST /search bodies returning paginated results

Fetch a person by email address to deduplicate inbound leads

GET STARTED

Start building with Copper CRM API API

Explore with Jentic

View OpenAPI Document

Use for: Create a new person in Copper with name, email and company, Search for people in Copper matching a specific tag, I want to fetch a Copper person record by their email address, Update an opportunity to move it to the next pipeline stage

Not supported: Does not handle email sending, marketing automation, or invoicing — use for CRM contact, opportunity and pipeline management only.

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

Jentic publishes the only available OpenAPI specification for Copper CRM API, keeping it validated and agent-ready. Copper is a CRM built on top of Google Workspace, and its developer API exposes 59 endpoints covering people, companies, leads, opportunities, projects, tasks, activities, pipelines, custom fields, related items and webhooks. Authentication requires three headers together: an API token, an X-PW-Application identifier and an X-PW-UserEmail value identifying the calling user. Search and fetch operations are POST-based with body filters, and pipeline-related endpoints expose pipelines, stages, contact types, customer sources and loss reasons for opportunity reporting.

Use Cases

Patterns agents use Copper CRM API API for, with concrete tasks.

★ Lead Capture from Marketing Forms

Marketing teams using Copper alongside their website forms can push every form submission straight into Copper as a lead. POST /people creates the contact, POST /people/fetch_by_email handles deduplication, and the leads endpoints take inbound leads through to qualification. Custom fields defined in Copper can be populated on creation to carry source, campaign and UTM data.

POST /people/fetch_by_email with the form submitter's email; if no match, POST /people to create the contact with the campaign UTM stored in a custom field.

Opportunity Pipeline Reporting

Sales operations teams can pull the live pipeline by listing pipelines, stages and opportunities, then aggregate by stage to drive forecast dashboards. POST /opportunities/search returns filtered opportunities, and the pipeline-stage and loss-reason endpoints provide the dimensional values to slice the report.

List pipelines, then POST /opportunities/search filtered to the 'Enterprise' pipeline and group results by pipeline stage to compute weighted forecast.

Activity Logging from Voice Tools

Voice and meeting platforms can log call summaries directly onto the relevant Copper person or company by creating activity records. The activities endpoints support custom activity types so teams can distinguish demo calls from check-ins, and webhooks alert the Copper UI when new activities appear.

Create an activity of type 'meeting' against the person matching the meeting attendee's email, with a summary string and the meeting date.

AI Sales Assistant via Jentic

An AI sales assistant agent can read incoming emails, classify the intent, and execute Copper updates such as creating a person, logging an activity or advancing an opportunity stage. Through Jentic, the agent never holds the API token or the X-PW-UserEmail header — both are injected at execution time from the vault.

Use Jentic to look up a person by email via POST /people/fetch_by_email and update their tags to add 'demo-scheduled'.

Key Endpoints

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

METHOD

PATH

DESCRIPTION

POST

/people

Create a person

POST

/people/search

Search or list people with filters

POST

/people/fetch_by_email

Fetch a person by email for deduplication

GET

/companies/{id}

Get a company by ID

GET

/account

Get the authenticated Copper account details

PUT

/people/{id}

Update a person

DELETE

/people/{id}

Delete a person

POST

/people

Create a person

POST

/people/search

Search or list people with filters

POST

/people/fetch_by_email

Fetch a person by email for deduplication

GET

/companies/{id}

Get a company by ID

GET

/account

Get the authenticated Copper account details

Why though Jentic?

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

Credential isolation

Copper requires three coordinated headers (X-PW-AccessToken, X-PW-Application, X-PW-UserEmail). Jentic stores all three in the credential vault and injects them together at execution time, so agents never see the access token and accidentally calling with the wrong user identity is prevented.

Intent-based discovery

Agents search Jentic with intents like 'create Copper person' or 'search Copper opportunities' and Jentic returns the matching POST search or upsert operation, complete with the body schema for filters and custom field definitions.

Time to first call

Direct integration: 3-5 days to handle the three-header auth, deduplication logic and webhook receivers. Through Jentic: under an hour from signup to a deduplicated person create.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Alternative

HubSpot CRM Objects API

Larger CRM platform with deeper marketing automation than Copper

Choose HubSpot when the team needs marketing hub features like landing pages and email nurtures alongside CRM.

Alternative

Salesforce API

Enterprise CRM with extensive customisation and a broader object model

Pick Salesforce when the customer needs enterprise governance, complex hierarchies and a wider AppExchange ecosystem.

Complementary

Slack API

Send sales notifications to channels when Copper webhooks fire

Pair Slack with Copper webhooks when sales teams want a 'deals-won' channel updated in real time.

Alternative

Zoho CRM API

Mid-market CRM alternative with a similar object model to Copper

Choose Zoho when the user is comparing mid-market CRM platforms and wants a non-Google-native option.

FAQs

Specific to using Copper CRM API API through Jentic.

Why is there no official OpenAPI spec for Copper CRM API?

Copper does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call Copper CRM 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 Copper CRM API use?

Copper requires three headers on every call: X-PW-AccessToken (the API key), X-PW-Application (the integration identifier) and X-PW-UserEmail (the calling user's email). All three are stored in the Jentic vault and attached together at execution time.

Can I deduplicate contacts when syncing leads into Copper CRM?

Yes. POST /people/fetch_by_email returns the existing person record if one is already attached to that email. Call it before POST /people so you upsert rather than duplicate when ingesting marketing form submissions.

How do I report on the Copper sales pipeline?

List pipelines and pipeline stages, then POST /opportunities/search filtered to the pipeline ID. Combine the results with the loss-reason and customer-source endpoints to attribute closed-lost deals and source channels.

What rate limits apply to the Copper CRM API?

The OpenAPI spec does not declare formal rate limits. Use webhook subscriptions for change events rather than polling, and implement retry-with-backoff on HTTP 429 responses to stay within Copper's documented per-minute caps.

How do I log a call against a person through Jentic with the Copper CRM API?

Run pip install jentic, search Jentic with 'log activity in Copper', load the operation schema for POST /activities and execute with the related person ID, activity type and summary text.