Pipedrive LeadFields API
Lead fields represent the near-complete schema for a lead in the context of the company of the authorized user. Each company can have a different schema for their leads, with various custom fields. In the context of using lead fields as a schema for defining the data fields of a lead, it must be kept in mind that some types of custom fields can have additional data fields which are not separate lead fields per se. Such is the case with monetary, daterange and timerange fields – each of these fields will have one additional data field in addition to the one presented in the context of lead fields. For example, if there is a monetary field with the key `ffk9s9` stored on the account, `ffk9s9` would hold the numeric value of the field, and `ffk9s9_currency` would hold the ISO currency code that goes along with the numeric value. To find out which data fields are available, fetch one lead and list its keys.
Pipedrive LeadFields API is one of 48 APIs that Pipedrive publishes on the APIs.io network, described by a machine-readable OpenAPI specification and an AsyncAPI event-driven specification.
Tagged areas include Lead Fields. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, an API reference, and an AsyncAPI specification.
This API exposes 1 operation across 1 path. It is described by OpenAPI 3.2.0, at version 1.0.0.
Requests are made against a single base URL, https://api.pipedrive.com/v1.
Metadata
The identity and technical contract details declared by the specification.
Authentication & Security 3
Pipedrive LeadFields API declares
3 security schemes
for authenticating requests.
It accepts HTTP basic authentication (basic_authentication).
An API key is passed in the header as x-api-token (api_key).
It supports OAuth 2.0 (oauth2) using the authorizationCode flow, exposing 27 scopes.
basic_authentication— Base 64 encoded string containing the clientid and clientsecret values. The header value should be Basic .oauth2— For more information, see https://pipedrive.readme.io/docs/marketplace-oauth-authorization
Paths & Operations 1
Across 1 path, the API surfaces 1 operation — 1 GET. Each is listed below with its method, path, parameters, and response codes.
Lead fields represent the near-complete schema for a lead in the context of the company of the authorized user. Each company can have a different schema for their leads, with vari…
Specification
The full machine-readable OpenAPI contract behind this narrative.
Source
More from Pipedrive 12
Other APIs Pipedrive publishes across the network.
This is an independent, third-party profile of Pipedrive LeadFields 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.