OVERALL CONTROL / 0.6-customer-control
Grades and scoring
Data access
25% of the overall score before applicability adjustment.
Scored answers and evidence
Read interface 7.5/10
Structured API for the declared product scope
Wrike / REST v4 tasks visible to an OAuth user, task create/update and task webhooks. BI Export, Datahub and native automation migration are separate routes.
Task objects are available within the acting user’s access.
Wrike Query Tasks ↗
Query Tasks response · Checked 2026-10-22
Bulk delivery 8.8/10
Batched or iterable API requests
Wrike / REST v4 tasks visible to an OAuth user, task create/update and task webhooks. BI Export, Datahub and native automation migration are separate routes.
Follow nextPageToken, carrying requested optional fields into each page.
Wrike Query Tasks ↗
nextPageToken and pageSize · Checked 2026-10-22
Query expressiveness 8.8/10
Documented structured API filters
Wrike / REST v4 tasks visible to an OAuth user, task create/update and task webhooks. BI Export, Datahub and native automation migration are separate routes.
Tasks support updatedDate and other structured filters.
Wrike Query Tasks ↗
Query parameters · Checked 2026-10-22
Access cost barrier 10.0/10
Access is free, or included in the lowest paid plan with no fixed access fee; published usage-only charges are eligible
Wrike / REST v4 tasks visible to an OAuth user, task create/update and task webhooks. BI Export, Datahub and native automation migration are separate routes.
API use is free on every plan; feature-specific entitlements still apply.
Wrike API FAQ ↗
API fees and subscription plans · Checked 2026-10-22
Third-party accessibility
20% of the overall score before applicability adjustment.
Scored answers and evidence
Third-party eligibility 10.0/10
Customer authorization without discretionary provider approval
Wrike / REST v4 tasks visible to an OAuth user, task create/update and task webhooks. BI Export, Datahub and native automation migration are separate routes.
Registered OAuth apps receive access after user consent; background apps retain user permissions.
Wrike API FAQ ↗
OAuth flow and background applications · Checked 2026-10-22
Downstream permission -
-
Wrike / REST v4 tasks visible to an OAuth user, task create/update and task webhooks. BI Export, Datahub and native automation migration are separate routes.
Applicable processing, AI-use and redistribution terms remain unresolved.
Wrike OAuth authorization ↗
Access route; downstream rights unresolved · Checked 2026-10-22
External action
15% of the overall score before applicability adjustment.
Scored answers and evidence
Write interface 7.5/10
Create and update in one business domain
Wrike / REST v4 tasks visible to an OAuth user, task create/update and task webhooks. BI Export, Datahub and native automation migration are separate routes.
Tasks can be created and updated with the required write scope.
Wrike Create Task ↗
Create Task (Folder) · Checked 2026-10-22
Wrike Update Task ↗
Documented update operation · Checked 2026-10-22
Custom application path 10.0/10
Customer applications using fixed APIs without provider selection
Wrike / REST v4 tasks visible to an OAuth user, task create/update and task webhooks. BI Export, Datahub and native automation migration are separate routes.
Customers can register integrations and obtain user-authorized OAuth tokens.
Wrike OAuth authorization ↗
Register application and authorization · Checked 2026-10-22
Continuity
15% of the overall score before applicability adjustment.
Scored answers and evidence
Refresh mechanism 7.5/10
Documented updated-since filters or webhooks
Wrike / REST v4 tasks visible to an OAuth user, task create/update and task webhooks. BI Export, Datahub and native automation migration are separate routes.
Task date filters and event subscriptions support ongoing extraction.
Wrike Query Tasks ↗
updatedDate · Checked 2026-10-22
Limit visibility 10.0/10
Published numeric quotas and recovery instructions
Wrike / REST v4 tasks visible to an OAuth user, task create/update and task webhooks. BI Export, Datahub and native automation migration are separate routes.
Guidance is approximately 400 requests/minute, assessed per second; back off on 429.
Wrike API FAQ ↗
Rate limits and pagination · Checked 2026-10-22
CDC and deletion capture 7.5/10
Updates and deletion identities documented for the stated resources
Wrike / REST v4 tasks visible to an OAuth user, task create/update and task webhooks. BI Export, Datahub and native automation migration are separate routes.
Task change events and TaskDeleted carry task identity.
Wrike webhooks ↗
TaskTitleChanged and TaskDeleted · Checked 2026-10-22
Replay and gap recovery 5.0/10
Bounded redelivery or overlapping queries; no durable consumer checkpoint
Wrike / REST v4 tasks visible to an OAuth user, task create/update and task webhooks. BI Export, Datahub and native automation migration are separate routes.
Retryable failures get up to three delivery attempts before suspension; retained replay is unverified.
Wrike webhooks ↗
Retries for Webhooks and Suspended Webhooks · Checked 2026-10-22
Data exit
20% of the overall score before applicability adjustment.
Scored answers and evidence
Export custody 7.5/10
Customer-held structured files or API records
Wrike / REST v4 tasks visible to an OAuth user, task create/update and task webhooks. BI Export, Datahub and native automation migration are separate routes.
Scoped API records can be held outside the provider.
Wrike Query Tasks ↗
Documented structured read response · Checked 2026-10-22
Post-cancellation access Disclosure
-
Disclosure only; does not reduce planned-exit credit.
Wrike / REST v4 tasks visible to an OAuth user, task create/update and task webhooks. BI Export, Datahub and native automation migration are separate routes.
The reviewed access docs do not establish contractual retrieval rights after cancellation.
Wrike OAuth authorization ↗
Access route; termination rights unresolved · Checked 2026-10-22
Planned migration fidelity 7.5/10
Portable structured records on documented routes; whole-product completeness unverified
Wrike / REST v4 tasks visible to an OAuth user, task create/update and task webhooks. BI Export, Datahub and native automation migration are separate routes.
Portable records are documented; complete native restore and history remain unverified.
Wrike Query Tasks ↗
Read response and declared object scope · Checked 2026-10-22
Business logic and customization
5% of the overall score before applicability adjustment.
Scored answers and evidence
Logic authoring 2.5/10
External integration code; native business logic portability not established
Wrike / REST v4 tasks visible to an OAuth user, task create/update and task webhooks. BI Export, Datahub and native automation migration are separate routes.
External code can use the scoped API; native workflow portability is not established.
Wrike OAuth authorization ↗
Application authentication · Checked 2026-10-22
Rights to custom logic -
-
Wrike / REST v4 tasks visible to an OAuth user, task create/update and task webhooks. BI Export, Datahub and native automation migration are separate routes.
Native workflow ownership and reusable export rights require a separate contractual review.
Wrike OAuth authorization ↗
Access route; native artifact rights unresolved · Checked 2026-10-22
Scores are out of 10. * Incomplete evidence discounts verified capabilities (unknown answers stay unknown). Planned migration drives data exit. Scoring method ↗
CUSTOMER CHOICE
Third-party accessibility
Users authorize OAuth apps within their Wrike access. Background integrations still act as a user; use the token response’s regional host.
Confirm who can connect, who owns the credentials and which uses are permitted. Customer consent and provider approval can be separate requirements; the selected plan and contract still matter.
READ / INTEGRATE
API and export routes
Traverse task pages with nextPageToken and retain optional fields on subsequent calls. updatedDate and other filters select records; shared access limits coverage.
| Access route | Authentication | Credential owner | Provider approval | Access requirement | Last checked |
|---|---|---|---|---|---|
| Customer-registered OAuth task integration | oauth2 | Customer | No | customer authorization | 2026-10-22 |
Availability depends on your product, plan and agreement. See the documentation below for the requirements of each route.
ECONOMIC ACCESS
Cost, authentication and limits
The API is free on all subscription plans, including Free. Paid features and fields keep their plan requirements; BI Export is outside this assessment.
Check API entitlement, credential ownership and rate limits for the route you intend to use. Include review fees, customer-plan upgrades and ongoing access charges in the total.
ACT FROM OUTSIDE
External action
Create tasks under folders and update task fields with write scopes. Supported fields depend on plan and access.
Validate the supported operation, acting identity and permission scope (read access does not imply write permission). Ambiguous retries and revoked credentials also affect whether an external workflow can run safely.
KEEP ACCESS USEFUL
Continuity
Task updates and TaskDeleted events identify changed records. Retryable failures receive up to three delivery attempts, then suspension; most 4xx responses suspend immediately.
CDC, deletions and recovery
| Question | Answer / applicable route | Evidence |
|---|---|---|
| Can ongoing extraction identify updates and deleted records on the declared route? | Updates and deletion identities documented for the stated resourcesWrike / REST v4 tasks visible to an OAuth user, task create/update and task webhooks. BI Export, Datahub and native automation migration are separate routes. Task change events and TaskDeleted carry task identity. | Wrike webhooks ↗TaskTitleChanged and TaskDeletedChecked 2026-10-22 |
| How can extraction recover after missed events or an interrupted consumer? | Bounded redelivery or overlapping queries; no durable consumer checkpointWrike / REST v4 tasks visible to an OAuth user, task create/update and task webhooks. BI Export, Datahub and native automation migration are separate routes. Retryable failures get up to three delivery attempts before suspension; retained replay is unverified. | Wrike webhooks ↗Retries for Webhooks and Suspended WebhooksChecked 2026-10-22 |
Useful ongoing access includes corrections and deletions, not only the first export. A failed request, changed filter or lost resource permission should not be interpreted as a deleted record.
LEAVE WITH YOUR DATA
Data exit and portability
Task JSON can be retained outside Wrike. This route does not establish complete attachments, history or independently runnable workflow definitions.
Test the output against the destination’s required fields and history. Check stable identifiers, relationships, attachments and extraction time; a sample file proves only the coverage of that sample.
BUILD / INSPECT / REUSE
Business logic and customization
Customers can write external integration code against the assessed API. Native workflow rights and independent execution remain unresolved (record access does not establish portable business logic).
Custom API access, ownership of workflows and the right to export their definitions are separate questions. A custom-app capability alone does not establish that business rules can move to another system.
AGREEMENTS / API DOCS / PROGRAM REQUIREMENTS
Documented conditions
Answers below come from public provider materials. Every answer retains its source check date, scope (a partner agreement does not describe every customer route). Customer contracts and live behavior still need verification.
| Question | Answer / applicable route | Evidence |
|---|---|---|
| What structured read interface is documented? | Structured API for the declared product scopeWrike / REST v4 tasks visible to an OAuth user, task create/update and task webhooks. BI Export, Datahub and native automation migration are separate routes. Task objects are available within the acting user’s access. | Wrike Query Tasks ↗Query Tasks responseChecked 2026-10-22 |
| How can customers retrieve data in bulk? | Batched or iterable API requestsWrike / REST v4 tasks visible to an OAuth user, task create/update and task webhooks. BI Export, Datahub and native automation migration are separate routes. Follow nextPageToken, carrying requested optional fields into each page. | Wrike Query Tasks ↗nextPageToken and pageSizeChecked 2026-10-22 |
| What queries can a customer issue outside the provider UI? | Documented structured API filtersWrike / REST v4 tasks visible to an OAuth user, task create/update and task webhooks. BI Export, Datahub and native automation migration are separate routes. Tasks support updatedDate and other structured filters. | Wrike Query Tasks ↗Query parametersChecked 2026-10-22 |
| Who decides whether a chosen third party may connect? | Customer authorization without discretionary provider approvalWrike / REST v4 tasks visible to an OAuth user, task create/update and task webhooks. BI Export, Datahub and native automation migration are separate routes. Registered OAuth apps receive access after user consent; background apps retain user permissions. | Wrike API FAQ ↗OAuth flow and background applicationsChecked 2026-10-22 |
| What extra commercial condition applies to the routes supplying the assessed read capability, relative to the lowest paid plan? | Access is free, or included in the lowest paid plan with no fixed access fee; published usage-only charges are eligibleWrike / REST v4 tasks visible to an OAuth user, task create/update and task webhooks. BI Export, Datahub and native automation migration are separate routes. API use is free on every plan; feature-specific entitlements still apply. | Wrike API FAQ ↗API fees and subscription plansChecked 2026-10-22 |
| Which external write operations are documented? | Create and update in one business domainWrike / REST v4 tasks visible to an OAuth user, task create/update and task webhooks. BI Export, Datahub and native automation migration are separate routes. Tasks can be created and updated with the required write scope. | Wrike Create Task ↗Create Task (Folder)Checked 2026-10-22 Wrike Update Task ↗Documented update operationChecked 2026-10-22 |
| How can customers connect an application they build or choose? | Customer applications using fixed APIs without provider selectionWrike / REST v4 tasks visible to an OAuth user, task create/update and task webhooks. BI Export, Datahub and native automation migration are separate routes. Customers can register integrations and obtain user-authorized OAuth tokens. | Wrike OAuth authorization ↗Register application and authorizationChecked 2026-10-22 |
| What mechanism supports repeatable extraction of changes? | Documented updated-since filters or webhooksWrike / REST v4 tasks visible to an OAuth user, task create/update and task webhooks. BI Export, Datahub and native automation migration are separate routes. Task date filters and event subscriptions support ongoing extraction. | Wrike Query Tasks ↗updatedDateChecked 2026-10-22 |
| How are integration limits disclosed? | Published numeric quotas and recovery instructionsWrike / REST v4 tasks visible to an OAuth user, task create/update and task webhooks. BI Export, Datahub and native automation migration are separate routes. Guidance is approximately 400 requests/minute, assessed per second; back off on 429. | Wrike API FAQ ↗Rate limits and paginationChecked 2026-10-22 |
| Where can a usable data copy be delivered? | Customer-held structured files or API recordsWrike / REST v4 tasks visible to an OAuth user, task create/update and task webhooks. BI Export, Datahub and native automation migration are separate routes. Scoped API records can be held outside the provider. | Wrike Query Tasks ↗Documented structured read responseChecked 2026-10-22 |
| What usable data or native definitions can leave before cancellation? | Portable structured records on documented routes; whole-product completeness unverifiedWrike / REST v4 tasks visible to an OAuth user, task create/update and task webhooks. BI Export, Datahub and native automation migration are separate routes. Portable records are documented; complete native restore and history remain unverified. | Wrike Query Tasks ↗Read response and declared object scopeChecked 2026-10-22 |
| What retrieval rights are documented at cancellation? | -Wrike / REST v4 tasks visible to an OAuth user, task create/update and task webhooks. BI Export, Datahub and native automation migration are separate routes. The reviewed access docs do not establish contractual retrieval rights after cancellation. | Wrike OAuth authorization ↗Access route; termination rights unresolvedChecked 2026-10-22 |
| How can customers define their own business logic? | External integration code; native business logic portability not establishedWrike / REST v4 tasks visible to an OAuth user, task create/update and task webhooks. BI Export, Datahub and native automation migration are separate routes. External code can use the scoped API; native workflow portability is not established. | Wrike OAuth authorization ↗Application authenticationChecked 2026-10-22 |
| What rights or portability are documented for custom workflow artifacts? | -Wrike / REST v4 tasks visible to an OAuth user, task create/update and task webhooks. BI Export, Datahub and native automation migration are separate routes. Native workflow ownership and reusable export rights require a separate contractual review. | Wrike OAuth authorization ↗Access route; native artifact rights unresolvedChecked 2026-10-22 |
| What permission is needed for the documented downstream use? | -Wrike / REST v4 tasks visible to an OAuth user, task create/update and task webhooks. BI Export, Datahub and native automation migration are separate routes. Applicable processing, AI-use and redistribution terms remain unresolved. | Wrike OAuth authorization ↗Access route; downstream rights unresolvedChecked 2026-10-22 |
SOURCES / SCOPE / HISTORY
Sources and open questions
This review is based on the documentation below. Live account behavior and customer-specific agreements haven’t been tested.
Still to confirm
- Applicable downstream terms where not established above
- Contractual post-cancellation retrieval rights
- Native workflow ownership, reusable definitions and complete product migration
Documentation
Assessment checked 2026-10-22. Each answer retains its source and applicable route; the check date does not establish live account behavior.