The docs for the response schemas are misleading as they list response model properties in camelCase whereas the reality is they are in snake_case.
This PR fixes the issue by listing the properties in snake_case.
Also, worth mentioning, that currently the query parameters (in the API examples the properties in the opts object) can be passed in snake_case as well as in camelCase.
Reported issue here: https://github.com/pipedrive/client-nodejs/issues/501
The docs for the response schemas are misleading as they list response model properties in camelCase whereas the reality is they are in snake_case.
This PR fixes the issue by listing the properties in snake_case.
Also, worth mentioning, that currently the query parameters (in the API examples the properties in the
opts
object) can be passed in snake_case as well as in camelCase.