Hello,
Is there an OpenAPI specification document somewhere which describes the api? (openapi.yaml or openapi.json)?
Cheers,
James
Hey @James Sewell, welcome to the Community!
I've just raised a Support ticket for you, someone should be in contact with you soon 😊
Hi Hugh,
I would also be interested in an OpenAPI specification of the API.
Thanks
Patrick
Hey @Patrick Heinzelmann, welcome to the Community!
At the moment, there is no OpenAPI specification available for our API. Your feedback has been passed on to the Product team. If anything changes, I'll be sure to let you know!
Has anything changed with this? Still no OpenAPI spec?
We're also interested in an OpenAPI specification.
Hi @Martin Severin Steffensen, welcome to the Community and thank you for adding your support here🙌🏼
@[Deleted User] Thanks for the welcome. I would just like to add to why an OpenAPI specification should be considered very important. There exists quite a few tools out there which lets us auto generate client-side source code to interact with any API with an associated OpenAPI specification. This reduces time spent developing by a significant amount and allows us to focus more on the actual product we're creating instead of creating the code for interacting with the API.
Is there any updated information available about what Wrike is thinking with regards to adding an OpenAPI specification to their API?
Thanks for getting back to me @Martin Severin Steffensen, I will pass on your feedback to the team. At the moment, we don't have any updates, unfortunately, but we'll be sure to let you know if anything changes.
Hi there, we are also interested in an OpenAPI specification !
Welcome to the Community @Olivier Metra 👋 We currently provide you with the Developers Portal where you can find all the available documentation concerning API 👍
Hi @Elizaveta Bogdanova, thanks !
An OpenAPI definition file file would help us to generate client-side code easily, see https://stoplight.io/openapi and would be added value to Wrike.
Lisa, this addition to Wrike would be a massive help for productivity and quality when integrating with Wrike.
We're not requesting an OpenAPI document for the sake of documentation, but for how various tooling allows us to automatically generate client-side code based on such a document instead of typing it out manually.
Thanks a lot for providing additional detail here, folks!
Open API would be very useful. Many applications can automatically create a connector if an OpenAPI is provided. I am wanting to use it specifically for Microsoft Power Automate and Power Apps.
Thank you for sharing your feedback @Seth Neds!
+1 for OpenAPI, please.
Providing an OpenAPI (Swagger) specification would make the maintenance of client API libraries much easier.
Thank you folks! No updates at the moment; I've sent your feedback to our team 👍
+1 for the OpenAPI specification, looking to start integrating with Wrike and struggle to believe this is missing.
There are tools available that are able to convert from Postman -> OpenAPI spec but they can't be used as the Postman examples all have hardcoded rather than parameterised queries, so a machine translation is impossible without lots of manual correction.
Seems a huge oversight not to have an industry-standard OpenAPI spec available.
Just another reminder that providing an OpenAPI specification would help authors of client API libraries keep in sync with changes to your public API.
Since I've started maintaining a simple integration tool with Wrike last year, I've already found portion of the API that differ from what the library I was using had implemented. Right now it's trial and error for me to figure out what's broken. If your team provided an OpenAPI specification, I wouldn't have to guess, the API would be self-documented.
Is there any update on this issue?
Really need this
The fact that something as basic as OpenAPI specifications has been an open request for five years is bananas.
What's even crazier to me is that people in this thread have made it very clear that OpenApi specs are not being requested for the sake of documentation - yet the stock answer is still "here's where you can find api information"
For any mods looking at this in the future: The reason people want OpenAPI specs is that the standardized definition lets them generate tooling and leverage api exploration tools to plan their work. Your docs (regardless of how thorough they are) will never meet that need.
Think of it like an adapter for your tools and code. A website with information for you to read and copy/paste can't be used as an adapter. A file with standardized definitions can be used an adapter. Instead of having to go find the endpoints you want to use and writing the code to manage requests to that endpoint or replace hard coded values with parameters and organize endpoints, I can just point a script at the OpenAPI docs and it will generate an entire toolbox for me to use without manually writing any integration connector code. wrike.integration.problemSolved()
Till this is available, I'm probably going to maintain my own spec. If I do, I'll post a github link here. We can maintain it as a community until the Wrike product team gets their head wrapped around why this is important. I recommend spending some time hanging with the engineers. They're cool.
Dear All,Please refer to the OpenAPI-compliant documentation released in July.https://developers.wrike.com/apiv4-schema-reference/
