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
WordPress / self-hosted WordPress REST API posts and post mutations; WordPress.com, plugin-specific fields, media bytes and whole-site migration are excluded.
WordPress exposes post records through its REST API. Authentication and permissions determine access to drafts, private posts and edit-context fields.
WordPress REST posts reference ↗
List Posts and query arguments · Checked 2026-10-22
Bulk delivery 8.8/10
Batched or iterable API requests
WordPress / self-hosted WordPress REST API posts and post mutations; WordPress.com, plugin-specific fields, media bytes and whole-site migration are excluded.
Traverse /wp/v2/posts using page/per_page, up to 100 records per page; total and total-page headers expose traversal bounds.
WordPress REST posts reference ↗
List Posts and query arguments · Checked 2026-10-22
Query expressiveness 8.8/10
Documented structured API filters
WordPress / self-hosted WordPress REST API posts and post mutations; WordPress.com, plugin-specific fields, media bytes and whole-site migration are excluded.
Post queries support date, author, status, search and taxonomy filters.
WordPress REST posts reference ↗
List Posts and query arguments · Checked 2026-10-22
Access cost barrier -
-
WordPress / self-hosted WordPress REST API posts and post mutations; WordPress.com, plugin-specific fields, media bytes and whole-site migration are excluded.
Minimum commercial entitlement and exact API charges were not established for the assessed route.
WordPress REST posts reference ↗
List Posts and query arguments · 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
WordPress / self-hosted WordPress REST API posts and post mutations; WordPress.com, plugin-specific fields, media bytes and whole-site migration are excluded.
Use application passwords over HTTPS for remote clients. Cookie authentication uses logged-in users and nonces; each operation retains WordPress capability checks.
WordPress REST authentication ↗
Application Passwords and Cookie Authentication · Checked 2026-10-22
Downstream permission -
-
WordPress / self-hosted WordPress REST API posts and post mutations; WordPress.com, plugin-specific fields, media bytes and whole-site migration are excluded.
Processing, AI-use, redistribution and other downstream contractual permissions were not settled by this technical review.
WordPress REST authentication ↗
Application Passwords and Cookie Authentication · 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
WordPress / self-hosted WordPress REST API posts and post mutations; WordPress.com, plugin-specific fields, media bytes and whole-site migration are excluded.
Create, update and delete posts through the posts API with the required user capabilities.
WordPress REST posts reference ↗
Create, Update and Delete a Post · Checked 2026-10-22
Custom application path 10.0/10
Customer applications using fixed APIs without provider selection
WordPress / self-hosted WordPress REST API posts and post mutations; WordPress.com, plugin-specific fields, media bytes and whole-site migration are excluded.
The documented interface can connect customer application code within its authorization and resource scope.
WordPress REST authentication ↗
Application Passwords and Cookie Authentication · 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
WordPress / self-hosted WordPress REST API posts and post mutations; WordPress.com, plugin-specific fields, media bytes and whole-site migration are excluded.
modified_after and modified_before select changed posts; post deletion notifications and retained replay are outside this review.
WordPress REST posts reference ↗
List Posts and query arguments · Checked 2026-10-22
Limit visibility -
-
WordPress / self-hosted WordPress REST API posts and post mutations; WordPress.com, plugin-specific fields, media bytes and whole-site migration are excluded.
A numeric request budget and recovery contract were not established by the reviewed references.
WordPress pagination contract ↗
Pagination Parameters and total headers · Checked 2026-10-22
CDC and deletion capture 5.0/10
Updates identified; deletion capture not established
WordPress / self-hosted WordPress REST API posts and post mutations; WordPress.com, plugin-specific fields, media bytes and whole-site migration are excluded.
Modified-date selection identifies current updates. Use full scans to reconcile missing posts; hard-delete events were not established.
WordPress REST posts reference ↗
List Posts and query arguments · Checked 2026-10-22
Replay and gap recovery 2.5/10
Rebuild from a fresh snapshot; no historical replay established
WordPress / self-hosted WordPress REST API posts and post mutations; WordPress.com, plugin-specific fields, media bytes and whole-site migration are excluded.
Repeat the declared collection or export route to rebuild current state within its permissions and selection limits. Deleted payloads and intermediate history are unverified.
WordPress REST posts reference ↗
List Posts and query arguments · 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
WordPress / self-hosted WordPress REST API posts and post mutations; WordPress.com, plugin-specific fields, media bytes and whole-site migration are excluded.
The assessed structured payloads can be retained in customer-held files. Broader contractual reuse rights remain unresolved.
WordPress REST posts reference ↗
List Posts and query arguments · Checked 2026-10-22
Post-cancellation access Disclosure
-
Disclosure only; does not reduce planned-exit credit.
WordPress / self-hosted WordPress REST API posts and post mutations; WordPress.com, plugin-specific fields, media bytes and whole-site migration are excluded.
The reviewed technical documentation does not establish retrieval rights after account termination.
WordPress REST authentication ↗
Application Passwords and Cookie Authentication · Checked 2026-10-22
Planned migration fidelity 7.5/10
Portable structured records on documented routes; whole-product completeness unverified
WordPress / self-hosted WordPress REST API posts and post mutations; WordPress.com, plugin-specific fields, media bytes and whole-site migration are excluded.
Retain the assessed structured records before losing access. Attachments, historical versions, permissions and full product configuration need separate extraction.
WordPress REST posts reference ↗
List Posts and query arguments · 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
WordPress / self-hosted WordPress REST API posts and post mutations; WordPress.com, plugin-specific fields, media bytes and whole-site migration are excluded.
External code can use this interface; native workflow portability was not established (API clients and native definitions are different artifacts).
WordPress REST authentication ↗
Application Passwords and Cookie Authentication · Checked 2026-10-22
Rights to custom logic -
-
WordPress / self-hosted WordPress REST API posts and post mutations; WordPress.com, plugin-specific fields, media bytes and whole-site migration are excluded.
Ownership and reusable export rights for native workflow artifacts need a separate contractual review.
WordPress REST authentication ↗
Application Passwords and Cookie Authentication · 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
Use application passwords over HTTPS for remote clients. Cookie authentication uses logged-in users and nonces; each operation retains WordPress capability checks.
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 /wp/v2/posts using page/per_page, up to 100 records per page; total and total-page headers expose traversal bounds. Post queries support date, author, status, search and taxonomy filters.
| Access route | Authentication | Credential owner | Provider approval | Access requirement | Last checked |
|---|---|---|---|---|---|
| self-hosted WordPress REST API posts and post mutations | HTTP Basic | Customer | No | Customer-supplied credentials | 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
Minimum plan and exact route fees remain unconfirmed.
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, update and delete posts through the posts API with the required user capabilities.
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
modified_after and modified_before select changed posts; post deletion notifications and retained replay are outside this review.
CDC, deletions and recovery
| Question | Answer / applicable route | Evidence |
|---|---|---|
| Can ongoing extraction identify updates and deleted records on the declared route? | Updates identified; deletion capture not establishedWordPress / self-hosted WordPress REST API posts and post mutations; WordPress.com, plugin-specific fields, media bytes and whole-site migration are excluded. Modified-date selection identifies current updates. Use full scans to reconcile missing posts; hard-delete events were not established. | WordPress REST posts reference ↗List Posts and query argumentsChecked 2026-10-22 |
| How can extraction recover after missed events or an interrupted consumer? | Rebuild from a fresh snapshot; no historical replay establishedWordPress / self-hosted WordPress REST API posts and post mutations; WordPress.com, plugin-specific fields, media bytes and whole-site migration are excluded. Repeat the declared collection or export route to rebuild current state within its permissions and selection limits. Deleted payloads and intermediate history are unverified. | WordPress REST posts reference ↗List Posts and query argumentsChecked 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
Retain the assessed structured records before losing access. Attachments, historical versions, permissions and full product configuration need separate extraction.
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. Native workflow rights and independent execution remain unresolved (record access does not establish portable application 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 scopeWordPress / self-hosted WordPress REST API posts and post mutations; WordPress.com, plugin-specific fields, media bytes and whole-site migration are excluded. WordPress exposes post records through its REST API. Authentication and permissions determine access to drafts, private posts and edit-context fields. | WordPress REST posts reference ↗List Posts and query argumentsChecked 2026-10-22 |
| How can customers retrieve data in bulk? | Batched or iterable API requestsWordPress / self-hosted WordPress REST API posts and post mutations; WordPress.com, plugin-specific fields, media bytes and whole-site migration are excluded. Traverse /wp/v2/posts using page/per_page, up to 100 records per page; total and total-page headers expose traversal bounds. | WordPress REST posts reference ↗List Posts and query argumentsChecked 2026-10-22 |
| What queries can a customer issue outside the provider UI? | Documented structured API filtersWordPress / self-hosted WordPress REST API posts and post mutations; WordPress.com, plugin-specific fields, media bytes and whole-site migration are excluded. Post queries support date, author, status, search and taxonomy filters. | WordPress REST posts reference ↗List Posts and query argumentsChecked 2026-10-22 |
| Who decides whether a chosen third party may connect? | Customer authorization without discretionary provider approvalWordPress / self-hosted WordPress REST API posts and post mutations; WordPress.com, plugin-specific fields, media bytes and whole-site migration are excluded. Use application passwords over HTTPS for remote clients. Cookie authentication uses logged-in users and nonces; each operation retains WordPress capability checks. | WordPress REST authentication ↗Application Passwords and Cookie AuthenticationChecked 2026-10-22 |
| What extra commercial condition applies to the routes supplying the assessed read capability, relative to the lowest paid plan? | -WordPress / self-hosted WordPress REST API posts and post mutations; WordPress.com, plugin-specific fields, media bytes and whole-site migration are excluded. Minimum commercial entitlement and exact API charges were not established for the assessed route. | WordPress REST posts reference ↗List Posts and query argumentsChecked 2026-10-22 |
| Which external write operations are documented? | Create and update in one business domainWordPress / self-hosted WordPress REST API posts and post mutations; WordPress.com, plugin-specific fields, media bytes and whole-site migration are excluded. Create, update and delete posts through the posts API with the required user capabilities. | WordPress REST posts reference ↗Create, Update and Delete a PostChecked 2026-10-22 |
| How can customers connect an application they build or choose? | Customer applications using fixed APIs without provider selectionWordPress / self-hosted WordPress REST API posts and post mutations; WordPress.com, plugin-specific fields, media bytes and whole-site migration are excluded. The documented interface can connect customer application code within its authorization and resource scope. | WordPress REST authentication ↗Application Passwords and Cookie AuthenticationChecked 2026-10-22 |
| What mechanism supports repeatable extraction of changes? | Documented updated-since filters or webhooksWordPress / self-hosted WordPress REST API posts and post mutations; WordPress.com, plugin-specific fields, media bytes and whole-site migration are excluded. modified_after and modified_before select changed posts; post deletion notifications and retained replay are outside this review. | WordPress REST posts reference ↗List Posts and query argumentsChecked 2026-10-22 |
| How are integration limits disclosed? | -WordPress / self-hosted WordPress REST API posts and post mutations; WordPress.com, plugin-specific fields, media bytes and whole-site migration are excluded. A numeric request budget and recovery contract were not established by the reviewed references. | WordPress pagination contract ↗Pagination Parameters and total headersChecked 2026-10-22 |
| Where can a usable data copy be delivered? | Customer-held structured files or API recordsWordPress / self-hosted WordPress REST API posts and post mutations; WordPress.com, plugin-specific fields, media bytes and whole-site migration are excluded. The assessed structured payloads can be retained in customer-held files. Broader contractual reuse rights remain unresolved. | WordPress REST posts reference ↗List Posts and query argumentsChecked 2026-10-22 |
| What retrieval rights are documented at cancellation? | -WordPress / self-hosted WordPress REST API posts and post mutations; WordPress.com, plugin-specific fields, media bytes and whole-site migration are excluded. The reviewed technical documentation does not establish retrieval rights after account termination. | WordPress REST authentication ↗Application Passwords and Cookie AuthenticationChecked 2026-10-22 |
| How can customers define their own business logic? | External integration code; native business logic portability not establishedWordPress / self-hosted WordPress REST API posts and post mutations; WordPress.com, plugin-specific fields, media bytes and whole-site migration are excluded. External code can use this interface; native workflow portability was not established (API clients and native definitions are different artifacts). | WordPress REST authentication ↗Application Passwords and Cookie AuthenticationChecked 2026-10-22 |
| What rights or portability are documented for custom workflow artifacts? | -WordPress / self-hosted WordPress REST API posts and post mutations; WordPress.com, plugin-specific fields, media bytes and whole-site migration are excluded. Ownership and reusable export rights for native workflow artifacts need a separate contractual review. | WordPress REST authentication ↗Application Passwords and Cookie AuthenticationChecked 2026-10-22 |
| What usable data or native definitions can leave before cancellation? | Portable structured records on documented routes; whole-product completeness unverifiedWordPress / self-hosted WordPress REST API posts and post mutations; WordPress.com, plugin-specific fields, media bytes and whole-site migration are excluded. Retain the assessed structured records before losing access. Attachments, historical versions, permissions and full product configuration need separate extraction. | WordPress REST posts reference ↗List Posts and query argumentsChecked 2026-10-22 |
| What permission is needed for the documented downstream use? | -WordPress / self-hosted WordPress REST API posts and post mutations; WordPress.com, plugin-specific fields, media bytes and whole-site migration are excluded. Processing, AI-use, redistribution and other downstream contractual permissions were not settled by this technical review. | WordPress REST authentication ↗Application Passwords and Cookie AuthenticationChecked 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
- Minimum commercial entitlement and exact API charges
- Downstream contractual permissions and post-cancellation retrieval rights
- Complete migration of history, files, permissions and native workflow definitions
Documentation
Assessment checked 2026-10-22. Each answer retains its source and applicable route; the check date does not establish live account behavior.