The migration guide says
We will gradually release new v2 APIs to replace the corresponding parts of v1 API. The corresponding v1 APIs will then be marked for deprecation and have a grace period of at least 1 year for migrations.
This is vague because “at least 1 year” could be 1 year or 100 years. Also, how are we to know when each v2 part became available and thus the clock started ticking on its deprecation?
We have a Pipedrive customer that has reported to us that v1 will be unavailable in April 2025.
What is needed here is a concrete set of dates as to when each part of the v1 API will become unavailable.
Seemingly innocuous statements such as: “Related objects have been removed from API responses to prevent too eager fetching of unnecessary data. Use subsequent API calls to fetch them if you still need them.” can have huge impacts. If the data we are currently retrieving in batches (e.g. page size of 100) will now be missing certain elements that were there in v1, now we will have to issue 100 or more API calls for each page of 100 records to get complete information. While it is laudable to prevent fetching unnecessary data, a better design would have been to at least include a way to specify to include the “unnecessary data” because for some of us the data is indeed quite necessary.