V1 endpoint return results in api v2 format

API
,
1

On pipedrive sandbox, when we access organization details endpoint, for example:
https://api.pipedrive.com/v1/organizations/41

response that we get is in v2 format:
{
“success”: true,
“data”: {
“id”: 48921,
“owner_id”: 18247138,
…
}
}

in v1 response(on different Pipedrive trial instance) owner_id is object as expected:
{
“success”: true,
“data”: {
“id”: 41,
“owner_id”: {
“id”: 21997590,
“name”: “xxx”,
“email”: “xxx”,
“has_pic”: 0,
“pic_hash”: null,
“active_flag”: true,
“value”: 21997590
},
…
}

So are you forcing api v2 response format even when we explicitly specify v1 in endpoint url for some Pipedrive instances? And issue is that our official library throw error in this case, because it expects owner_id to be object, not int.

I also tested via Postman too, and confirm that when accessing organization v1 endpoint only on this Pipedrive instance, we get response in api v2 format.

So my question is if this is configuration thing or is there a way to enable support for v1 too?

2

Hi! We are not enforcing v2 format on existing v1 endpoints so let’s try to troubleshoot this.

Can you please first confirm you’re not adding strict_mode=1 parameter to the request - it replaces objects with IDs.

If the above is not the reason then please share the instance/company domain with me via DM and we can dig deeper.

3

I am not applying any query parameters to URL in Postman when I am testing except api token, so whole url is like:
https://api.pipedrive.com/v1/organizations/48921?api_token=zzz
And I am getting just owner_id, not whole project.
Issue is on all API calls, and other data too - everything is acting like v1 is replaced with v2 responses.

4

I’ve also seen changes to some dateTime properties in v1 API.
I’ve not noted it down, but I think it was in the Filters API.

5

No longer the case for the Filters API…

6

I should also mention it only does it in with a sandbox account, not a ‘real’ one

7

Ok, now I’m sure it’s changing.

here is the value recorded 19/03/2025 :

      {
        "id": 1,
        "name": "All open deals",
        "filter_code": null,
        "is_editable": true,
        "active_flag": true,
        "type": "deals",
        "temporary_flag": null,
        "user_id": 23462083,
        "add_time": "2025-03-05 10:26:16",
        "update_time": null,
        "visible_to": "7",
        "last_used_time": null,
        "custom_view_id": null
      }

Here is the same one returned today 21/03/2025 :

      {
        "id": 1,
        "name": "All open deals",
        "filter_code": null,
        "is_editable": true,
        "active_flag": true,
        "type": "deals",
        "temporary_flag": null,
        "user_id": 23462083,
        "add_time": "2025-03-05T10:26:16.000Z",
        "update_time": null,
        "visible_to": "7",
        "last_used_time": null,
        "custom_view_id": null
      }

add_time has changed return format…