How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Copper People API

People (contacts) management

Copper People API is one of 7 APIs that Copper publishes on the APIs.io network, described by a machine-readable OpenAPI specification and an AsyncAPI event-driven specification.

Tagged areas include People. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, authentication docs, a getting-started guide, an AsyncAPI specification, and a JSON-LD context.

This API exposes 5 operations across 3 paths, and defines 5 schemas. It is described by OpenAPI 3.2.0, at version 1.0.

Requests are made against a single base URL, https://api.copper.com/developer_api/v1.

5 operations 3 paths 5 schemas 1 DELETE1 GET2 POST1 PUT

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
1.0
Base URL
https://api.copper.com/developer_api/v1
Authentication
API Key, API Key, API Key
Resource Areas
1

Authentication & Security 3

Copper People API declares 3 security schemes for authenticating requests. An API key is passed in the header as X-PW-AccessToken (PWAccessToken). An API key is passed in the header as X-PW-Application (PWApplication). An API key is passed in the header as X-PW-UserEmail (PWUserEmail). By default, every request must be authenticated.

  • PWAccessToken — API access token for the user
  • PWApplication — Application identifier, set to 'developerapi'
  • PWUserEmail — Email address of the API token owner

Paths & Operations 5

Across 3 paths, the API surfaces 5 operations — 1 DELETE, 1 GET, 2 POST, 1 PUT. Each is listed below with its method, path, parameters, and response codes.

People 5

People (contacts) management

POST
/people/search
Search People
searchPeople body → 200401429
POST
/people
Create a Person
createPerson body → 200
GET
/people/{id}
Get a Person
getPerson 1 param → 200
PUT
/people/{id}
Update a Person
updatePerson 1 param body → 200
DELETE
/people/{id}
Delete a Person
deletePerson 1 param → 200

Schemas 5

The contract defines 5 schemas that model the data the API accepts and returns. The most detailed are Person (21 properties), PeopleSearchRequest (8 properties), Address (5 properties), Error (2 properties). Each schema is shown below with its type and property counts.

Person
object
21 properties
CustomFieldValue
object
2 properties
Error
object
2 properties
Address
object
5 properties
PeopleSearchRequest
object
8 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

copper-people-api-openapi.yml Raw ↑

Other APIs Copper publishes across the network.

Copper Activities API
Copper Companies API
Copper Leads API
Copper Opportunities API
Copper Tasks API
Copper Webhooks API
Where this information came from

This is an independent, third-party profile of Copper People API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.