This directory contains detailed documentation for the WrikeXPI project. The documents herein cover API specifications, authentication mechanisms, and other relevant integration guides.
WrikeXPI had been developed with the goal to complement Wrike’s existing offering, level it up and make more integration possible. Here are a few key features:
| API | Auth Method |
|---|---|
| Wrike API | Permenant Token, OAuth with Expiry |
| Wrike XPI | Permenant Token, OAuth with Expiry Permenant OAuth Token, Basic Authentication |
The transparent proxy works the same way as Wrike API (https://developers.wrike.com/apiv4-schema-reference/), except that instead of using Wrike’s URL (e.g. https://app-eu.wrike.com/api/v4), change the URL to:
[!TIP]
The transparent proxy needs XPI Token instead of Wrike API Token, please retrieve it at the XPI Token Service (refer to next section).
Below is a list of available documentation:
How to use OAuth: A comprehensive guide to understanding and implementing the OAuth 2.0 flow for the WrikeXPI API. This document outlines the step-by-step process for authenticating users and obtaining access tokens.
API Specification: WrikeXPI API specification in OpenAPI 3.0 format.
Web-based API Playground: For easy validation and evaluation of XPI.
Please use the following to get your XPI Token to be used in the API Playground:
[!NOTE]
Due to the nature of Wrike’s API session design, when a new token is generated, the old will be invalidated.
Hence, please keep your token if you need it for long term usage and do not regenerate new one unless you would like to terminate the previous generated token.
note: We are still cleaning up the API specification document, you may see some internal codenames at the moment, you may safely ignore them for now!
Please refer to these documents to gain a deeper understanding of the WrikeXPI project’s technical components and to assist with your development and integration efforts.