A litte bit more about the use case:
We have developed a standard integration which we were suppose to deploy for a customer using Pipedrive. However, it fails because of this not expected change in label id.
Thanks for having a look at the documentation page as well
Thanks for your patience We were able to replicate the scenario. The confusion seems to arise from the fact that the value for label is more of a default but not a constant.
The value Customer does not change unless the account has some other language than English while setting it up. For instance, Customer becomes Klient if the account has been provisioned with Eesti as the language. So it is a default which depends on the localization setting but not a constant value that you can rely on.
The IDs are dynamic. So you can’t rely on them either.
My recommendation is to provide a configuration page for users to choose the right value. Much better if you already have a config page and this could go as a section there. I understand that it would be an additional step however it works much more reliably.
I have taken note of the feedback and the documentation page is also updated
That’s right. Unfortunately, you need to make 2 API calls to figure out the text value for the labels.
However, you can store these values in a dictionary to avoid making the call every time. The IDs once generated will not change. Nevertheless, this is feedback for the API design and I’ve taken note of it