Possible limitations when using beta API endpoints?

devpd
devpd Member Posts: 3 VERIFIED MEMBER
Name Dropper First Comment
in Apps and Integrations #1

Hi!

I've reviewed the API reference and searched in the community, but haven't been able to find details about what "beta" means in the context of the Pipedrive API.

What are the limitations or risks of using beta API endpoints such as "Get all deals (BETA)", "Get all persons (BETA)" and "Get all organizations (BETA)" in a production integration?

Are there any plans to make major changes to these endpoints? And is there a timeline for when they will be released out of beta? Thanks!

Tagged:

Answers

  • dimka
    dimka Pipedrive Team Posts: 1 PIPEDRIVE TEAM
    First Comment Photogenic First Anniversary
    #2

    Hi!

    The BETA for v2 endpoints means that we are collecting feedback from API users. While we aim to avoid introducing any breaking changes to the APIv2 endpoints, the general API change management policy does not apply to the BETA endpoints. We have not yet published the APIv2 roadmap, but we plan to drop the BETA status before the end of 2024.

  • devpd
    devpd Member Posts: 3 VERIFIED MEMBER
    Name Dropper First Comment
    #3

    Thank you for the information @dimka !

  • devpd
    devpd Member Posts: 3 VERIFIED MEMBER
    Name Dropper First Comment
    #4

    Hi @dimka!

    Having reviewed the API documentation further for "Get all deals", it seems that the v2 endpoints are generally recommended to be used as v1 will be deprecated.

    However based on the docs the v2 endpoint does not have a query parameter for "filter_id". Is it possible to apply filters to this endpoint? Thanks in advance!

  • dimka
    dimka Pipedrive Team Posts: 1 PIPEDRIVE TEAM
    First Comment Photogenic First Anniversary
    #5

    Hi @devpd !

    Thank you for bringing this to our attention! I want to confirm that "Get all deals" v2 endpoint does support the filter_id parameter. We apologize for the oversight in our documentation, update is on its way!

    In the meantime, you can utilize filter_id in your API requests as intended.

  • Daniel Serrano
    Daniel Serrano Member Posts: 3 NEW MEMBER
    First Comment
    #6

    I have been trying to use v2 of the POST method to add a new organization https://developers.pipedrive.com/docs/api/v1/Organizations#addOrganization and I always get a 400 no matter what. My guess is that there is something that is failing validation on the other side, but I have tried to create an org with the very basics and got the 400 as well. Bu very basics I mean:

    data = {"name": name, "owner_id": OWNER_ID, "visible_to": "3" }
    name and OWNER_ID being str

    I am being forced to use v1 for creating new orgs

  • Tony Xavier
    Tony Xavier Pipedrive Team Posts: 204 PIPEDRIVE TEAM
    25 Answers 100 Comments 25 Likes Second Anniversary
    #7

    Hello @Daniel Serrano,

    For the owner_id and visibile_to parameters, could you try to format them as integers and send the request without the values being added in double quotes? So it would be something like:

    { "name": "Pipedrive OU", "owner_id": 13840680, "visible_to": 3}

Categories