OpenAPI Specification now available for Wrike public APIs

Hi Wrike API users,

I’m Anmol Shrivastava, Senior Product Manager at Wrike, focusing on our public APIs and developer experience. I’m excited to announce the launch of OpenAPI Specification & [New] Schema Reference for Wrike’s Public APIs.

You can now access it under API reference v4 > [New] Schema Reference

What’s New?

While the API endpoints and functionality remain unchanged, the new schema unlocks several powerful benefits:

Downloadable OpenAPI Spec: Get the full OpenAPI specification to explore and integrate Wrike APIs using your favorite tools.
In-browser Try it out option: Quickly test endpoints directly from your browser without switching platforms.

No Functional Changes

This update does not introduce any new API endpoints or breaking changes. It simply makes the existing methods available in a widely adopted and developer-friendly format.

Going forward, the [New] Schema Reference page will serve as the primary source for all Wrike public APIs. We recommend starting using this update to ensure continuity and take advantage of improved usability.

Find more posts tagged with

Comments

Joesph Hoffmann

Love the YAML specification--this is a huge step forward! One question: I’m not sure how the “Try it out” feature is supposed to work. The server response always ends in a CORS network failure for me, so I feel like I may be missing a configuration step.

That said, the documentation is super helpful, and I really appreciate how it auto-generates cURL examples and the full request URL structure. This will definitely speed up development. Thank you!

Anmol Shrivastava

Hey @Joesph Hoffmann glad to hear you're excited about using the OpenAPI spec!
To resolve the error you're seeing, please make sure to add your token by clicking the Authorize button (refer to the attached screenshot).

That should fix the issue, but feel free to reach out if the error persists - happy to help!
Thanks again.

Joesph Hoffmann

Awesome! Works perfectly. I don't know how I missed that giant blue button at the top. Thanks!

ChoongSeng Chen

Now and then I got this error too when using the page on https://developers.wrike.com/apiv4-schema-reference/ to execute API calls from the page itself.

{  <span class="hljs-attr">"errorDescription"</span>: "Failed to authorize CORS request",  <span class="hljs-attr">"error"</span>: "not_authorized"}

Doing this in my API Apps resolved the problem:

Add https://developers.wrike.com/ to the HTTP access control (CORS) for the API app.

I think somehow the CORS aren't "globally whitelisted" for the API page.

Rohan V

Hi @ChoongSeng Chen, I’m sorry to hear that you encountered this error, and thank you for sharing your experience. We’ll pass your comment along to the relevant team for review 👍

Gretchen Linder

I'm getting an error when using this for get spaces. I selected an accessTypes value of "Public" and I get the "Parameter accessTypes value is invalid" error. The code line produced in the [New] Schema Reference is this:

https://www.wrike.com/api/v4/spaces?withArchived=false&withInvitations=false&accessTypes=Public

When I run this same line in Postman, it produces the same error. When I add square brackets around "Public" it works as expected. The successful line looks like this:

https://www.wrike.com/api/v4/spaces?withArchived=false&withInvitations=false&accessTypes=[Public]

Am I not setting something correctly on the [New] Schema Reference page?

Rohan V

Hi @Gretchen Linder, really sorry for the late response. As I can see, you were able to get in touch with the support team. I hope they were able to assist you. If you need anything else or have any other questions, feel free to let us know 👍