Do I need a developer to use the Pipedrive API?
Not to look around. With your API token and Postman you can read deals in minutes. You do need one for anything that runs unattended: a webhook handler, a scheduled sync, a write into another system. That code has to cope with retries, limits and bad data, and keep doing it for years.
Does Pipedrive have rate limits on API calls?
Two kinds. A daily token budget for the whole company, set by plan and seats, and a burst limit per token over a rolling 2-second window. Search has its own cap of 10 requests per 2 seconds. Hitting either returns 429. The ledger above shows how a typical sync spends the budget.
Can the Pipedrive API reach custom fields?
Yes, on deals, persons, organizations, products and activities. Each one has a generated key rather than its label, so look the keys up through the fields endpoints and store them. In v2, custom field values sit in their own custom_fields object.
Is there an official Pipedrive API documentation site?
Yes, developers.pipedrive.com has the endpoint reference for v1 and v2, plus guides on authentication, rate limits, webhooks and the v2 migration. We build against those docs rather than guessing at behavior.
Are there official Pipedrive API client libraries?
Pipedrive publishes two official clients, for Node.js and PHP. From Python or anything else, plain HTTPS requests with the x-api-token header or an OAuth bearer token work fine.
Should new code use API v1 or v2?
v2 wherever the endpoint exists. It costs fewer tokens per call and is stricter about input. Fall back to v1 only for objects that haven't moved yet, and expect to port those calls later.