What we do
Tools
Industries
Department
How we workLet's talk →
Home/Wrike/Wrike API
Wrike developer reference

The Wrike API v4: First Call, Tokens, Rate Limits and Webhooks

Wrike's REST API reaches folders, projects, tasks, custom fields, comments, attachments, time logs and users, with webhooks for changes. This page covers what you need while you build, starting with the one thing that trips up almost everyone: your account's data lives on a regional host.

From no token to a working Wrike API call

  1. 1

    Create an app in the App Console

    Open Wrike's App Console and create an app. That gives you a client ID and secret for OAuth, and a place to make a permanent token.

  2. 2

    Get a token

    For a script that acts as you, click Get token on the app and enter your password. Copy it at once: Wrike shows a permanent token only one time. For an app other people sign in to, use OAuth 2.0 (next section).

  3. 3

    Find your host

    Wrike keeps accounts in US and EU data centers. The OAuth token response includes a host field, and every call goes to https://{host}/api/v4. With a permanent token, use the host your account opens on.

    Watch for: a 401 on a token you know is valid usually means the wrong host, not a bad token.

  4. 4

    Make the first call

    Send GET /contacts?me=true with Authorization: bearer {token}. It returns your own user record, which proves the token, the host and the account in one request.

  5. 5

    Read something real

    List GET /folders to see the folder tree. In Wrike, a project is a folder with project details attached, so projects come back from the folder endpoints too. Tasks live under GET /folders/{folderId}/tasks or GET /tasks.

Permanent token or OAuth 2.0 for Wrike

Single-user

Permanent access token

  • Never expires, so there's no refresh logic to write.
  • Acts as the person who created it, with exactly their access.
  • Made in the App Console and shown once. Revoke it there too.
  • Dies when that person resets their password, is deactivated, or an admin uses Log in as this user.
Multi-user apps

OAuth 2.0 authorization code

  • Send people to login.wrike.com/oauth2/authorize/v4; the returned code is valid for 10 minutes.
  • Swap it at login.wrike.com/oauth2/token for an access token that lasts one hour.
  • Each refresh returns a new refresh token and voids the old one. Store the new one every time.
  • Request only the scopes you need; each method's reference lists the scopes it requires.

For a production integration that runs unattended, create the permanent token under a dedicated integration user, not a staff member, or the sync stops the day they reset their password.

Wrike rate limits and paging

Wrike's developer FAQ puts the limit at roughly 400 requests a minute, and its help center lists that per user alongside a ceiling of 5,000 a minute from one IP address. Over the limit you get a 429. Wrike's advice is to retry with exponential backoff, which matters more here than on APIs that tell you exactly how long to wait.

Lists are paged. GET /tasks returns up to 1,000 tasks by default; set pageSize (1,000 at most) and pass the nextPageToken from each response into the next request. If you asked for optional fields such as customFields or responsibleIds on the first page, send them again on every page after it.

Custom fields are identified by 16-character IDs, and the customFields filter matches on those IDs with a comparator such as EqualTo or InRange. Look the IDs up once at startup and fail loudly if one has gone, rather than writing blanks after someone renames a field.

Wrike webhook behavior that catches builders out

Create webhooks at three levels: POST /folders/{folderId}/webhooks, POST /spaces/{spaceId}/webhooks, or POST /webhooks for the whole account.

Unsigned events

How you'll know: Anything that can reach your URL can post fake task changes to it.

Fix: Pass a secret when you create the webhook. Wrike then signs each payload with HMAC-SHA256 in X-Hook-Signature. During the handshake, reply with an HMAC of the X-Hook-Secret value Wrike sends, keyed with your secret, not with the raw value.

Suspended after a single 400

How you'll know: Events stop, and the only notice is an email to whoever created the webhook.

Fix: Most 4xx responses (all except 408 and 429) suspend the webhook immediately, with no retry. Retryable errors get three attempts first. Always return 200 quickly and queue the work; check status with GET /webhooks and resume with a PUT setting the status back to active.

Bulk changes that never arrive

How you'll know: Someone imports or mass-edits 200 tasks and your copy doesn't change.

Fix: Mass actions, including imports, don't fire webhook events. Run a scheduled comparison against updatedDate to pick up what events skip.

Webhooks gone with the person who made them

How you'll know: A sync built months ago stops completely after a staff member leaves.

Fix: Deleting a user deletes their webhooks. Create them under the same dedicated integration user that holds the token.

The same event twice

How you'll know: Duplicate comments or double-counted time entries in the other system.

Fix: Payloads arrive as a JSON array, and duplicates are possible. Use the Idempotency-Key header to drop repeats before acting.

Which piece of Wrike to use for the job in front of you

If the job is… Reach for You still own
Assign a reviewer when a task status flips Wrike's automation engine, set up in the workflow itself. Our Wrike automation page covers it. Keeping the rule in step as statuses and teams change. No code involved.
Post to a Slack or Teams channel when a project moves Wrike's own Slack or Microsoft Teams integration. Choosing which projects and events are worth a message, so the channel stays readable.
Mirror custom fields into Salesforce or HubSpot, both ways Code on the REST API, with webhooks in and API writes out. Field IDs, conflict rules when both sides change, the webhook receiver and the catch-up job.
Turn emailed requests into Wrike projects from the right blueprint An intake service on the API that reads the email and creates the project. Deciding which request maps to which blueprint, owner and custom field values.
Ask an AI assistant what is overdue across your spaces Wrike's hosted MCP server, inside the signed-in person's own permissions. Checking what it changes. It acts for one person, not as an unattended sync.

Questions people ask

Does Wrike have a public API?

Yes. API v4 is a public REST API covering folders, projects, tasks, custom fields, comments, attachments, time logs and users, with webhooks for change events. Apps and tokens are created in Wrike's App Console.

What does Wrike connect to natively?

Wrike lists connectors for Salesforce, Slack, Microsoft Teams, Outlook, HubSpot and SharePoint, among others. They handle a notification or a basic link between records well. Two-way updates and your own custom fields are where the API comes in, and that's the part n-frames builds.

Is there a Wrike MCP server for connecting AI tools?

Yes. Wrike runs an official hosted MCP server that lets AI assistants such as Claude or ChatGPT work with Wrike data, limited to what the signed-in user can already see. For scheduled syncs between systems, the REST API is still the right tool.

Do I need a developer to use Wrike's API?

For a one-off script that pulls a report, a technical person with a permanent token can manage. Anything that runs unattended needs someone who'll handle regional hosts, refresh-token rotation, 429 backoff and webhook suspension, because each of those fails quietly.

What's the difference between the Wrike API and Wrike's own automation engine?

The automation engine runs inside Wrike, triggered by Wrike events and acting on Wrike data. The API is how anything outside Wrike reads or writes it. Most setups use both: rules for what stays in Wrike, API code for what has to reach another system.

What is the Wrike API rate limit?

About 400 requests a minute per user, with a 5,000-a-minute ceiling per IP address according to Wrike's help center. Over the limit, the API returns 429, and Wrike recommends retrying with exponential backoff.

How do I verify that a Wrike webhook came from Wrike?

Register the webhook with a secret. Wrike signs each request body with HMAC-SHA256 and sends it in X-Hook-Signature. Compute the same HMAC over the raw body and reject anything that doesn't match.

Keep reading

Wrike Integrations That Carry Hours to Billing Wrike integrations explained: the Salesforce add-on, Wrike Sync, Wrike Integrate, Zapier and the API, and how logged hours reach your invoicing tool.Wrike Automation Rules, and What They Ignore How Wrike automation rules work: triggers, conditions, up to 10 actions, plan allowances per seat, and the changes rules never see, such as API edits.Wrike Dashboard vs Analyze Wrike dashboards, Analyze and BI feeds compared by plan: widget limits, refresh times, sharing, exports, and getting revenue beside project status.Wrike Time Tracking by Plan, Seat and Timer Where Wrike's timer is, how to log hours after the fact, which plans get Timesheets and approvals, and why a week's total can look wrong.Wrike Gantt Dependencies and the Critical Path Which Wrike plan gets dependencies, critical path and baselines, how the four link types move dates, and why a task in the chain didn't shift.Wrike vs Asana Wrike vs Asana, decided by why last quarter's projects slipped: overbooked people or a tool nobody updated. Plans, prices, moving across, and request intake.Asana API An Asana API reference: PAT vs OAuth vs service accounts, rate limits by plan, offset pagination, and webhooks from the handshake to signature checks.Salesforce REST API How the Salesforce REST API works now: external client apps and OAuth flows, the daily API allowance per org, composite requests and Bulk API 2.0.Zapier Webhook Setup How to catch a webhook in Zapier, send POST, GET or custom requests out, which plans include Webhooks by Zapier, and why hooks fail without warning.

Let's talk

Tell us the one thing your team does manually that eats up time. We read every message and reply within a day.