pipedrive openapi file issues
One of the reasons we went for pipedrive was a well documented api via openapi
Using the api file we can generate the clients for node in typescript.. however there is 1 issue, as the file does not make use of the component definitions non of the non-java generators are able to generate well written types.
When the models are abstracted away into the components this all changes.
Is the dev team at pipedrive aware of this limiting factor?
In addition, there is an npm package for a pipedrive client but there are no types for typescript included which would have been the alternative.
`
Notice!
This API is under active maintenance, and we are constantly adding new functionality to this version. Follow @PipedriveDev and check our Changelog for updates.
`
This would not be too much of an issue, but the 1st thing you read on the REST API docs is a big old warning saying the API could change...
Comments
-
In addition, using the typescript-axios generator from the official page https://openapi-generator.tech/docs/usage#generate
Creates a file with lots of errors.
0 -
Hi @John Carmichael , for this specific matter I recommend reaching out to the developer community, who will be best suited to help you 👩💻
0
