Migration from v1 to v2 API

API
1

Hi Pipedrive Team :waving_hand:

Sorry if this question has already been asked - I wasn’t able to find any relevant information on the forum.

We’re currently using your API (v1) and just noticed while you’ve introduced a v2 version, there is a one-year grace period for the v1 API (according to your documentation: Pipedrive API v2 overview)

We’re planning to migrate all our code to v2, but we want to ensure that all the endpoints we currently use are available in the new version. So far, we use the following endpoints:

  • organizations
  • organizationFields
  • personFields
  • deals
  • dealFields
  • users

We’ve noticed that the following endpoints have not yet been migrated to v2:

  • organizationFields
  • personFields
  • dealFields

We’re aiming for a one-time migration from v1 to v2. Is there a specific deadline for each of these endpoints after which they will no longer be available? We want to avoid a situation where one of the v1 endpoints suddenly becomes unavailable.

Thank you in advance!

2

I am also stuck on this, I need to keep using

  • organizationFields

  • personFields

  • dealFields

  • productFields

Can anyone provide some help please?

3

I’m also have this issue. I just spent a few weeks working on the migration and checking everything field by field, how they change etc and adapting them to handle the new schema while supporting the v1 schema as well (E.g. Leads).

It would be helpful to have more development on the API, it’s really framented at this point and pretty hard to build from scratch unless you’re specialized in Pipedrive. I’ve been creating in the Pipedrive API for around 8 years and even for me at this point it takes a lot of effort to keep the integration solid with this v1 to v2 transition.

4

Looks like this is now possible with the recent update: https://developers.pipedrive.com/changelog/post/introducing-new-fields-api-v2

1 Like