we found a workaround to our specific case, but when I try create a note with the same input, my browser “understands” what it should be, but the link itself is still with %%20
I got created note in response and it included the same content I created it with (nothing was changed).
If I make GET /notes/<created note id> I’m getting the same result.
Did I get right that, if you do the same operation (let say with Postman) the content changes for you and the content you sent during creating does not equal to what you get in following GET request?
If so, could you provide a payload you send (code block like I did above), so I could try it too?
I did not know that I could send parameters as json, because the official docomentation says it should be x-www-form-urlencoded, (https://developers.pipedrive.com/docs/api/v1/pipedrive-api.yaml line 3816), and the pipedrive node sdk that we are using also sends the parameters using content-typeapplication/x-www-form-urlencoded
@lxlvm thank you for your explanation. Indeed, OpenAPI file says to use application/x-www-form-urlencoded content type for a POST /notes request body, which is true, but it also supports application/json . We have this statement in docs (Requests)
We recommend using JSON body format when performing API requests. In order to do a proper JSON-formatted request, make sure you provide Content-Type: application/json in HTTP request headers.
For the POST method, regular form-encoded body format is also supported but you may experience quirks related to lack of data types
but I agree, ideally, it should be reflected in OpenAPI file too.