WOOCOMMERCE LEGACY REST API
WooCommerce Legacy REST API compatibility with REEID Translate
WooCommerce Legacy REST API compatibility with REEID Translate is being evaluated from available plugin evidence. Restores the removed WooCommerce Legacy REST API in WooCommerce 9.0 and later. No specific visitor-facing translation surface is currently confirmed.
AWAITING VERIFICATION
What the available evidence establishes for WooCommerce Legacy REST API.
Official plugin information supports the compatibility context documented for this category.
AWAITING VERIFICATION
This integration has not yet been manually verified by REEID.
PLUGIN PROFILE
WooCommerce Legacy REST API is documented in the Other category with 5 concrete capabilities identified in the current evidence.
EVIDENCE COVERAGE
Plugin capabilities are documented from available official evidence. Translation support is listed only when concrete visitor-facing content is explicitly established.
COMPATIBILITY REVIEW
How WooCommerce Legacy REST API compatibility is evaluated
01 · Review official plugin evidence
Establish documented plugin behaviour before making any multilingual compatibility claim.
02 · Identify visitor-facing content
Determine whether the documented behaviour exposes human-readable values that visitors can see.
03 · Separate content from functionality
Keep structure, configuration, logic, integrations and runtime behaviour outside translation scope unless concrete content values are identified.
04 · Confirm translation scope
Publish supported content only when concrete visitor-facing values are explicitly established and can be validated.
PLUGIN INTELLIGENCE
What the official plugin evidence shows
Plugin capabilities
- Restores the removed WooCommerce Legacy REST API in WooCommerce 9.0 and later.
- Keeps existing user keys working with the Legacy REST API.
- Leaves WooCommerce 8.9 and earlier unchanged by detecting the built-in Legacy REST API and not initializing itself.
- Is not compatible with High-Performance Order Storage.
- Provides the same endpoints and behavior as the Legacy REST API in WooCommerce 8.9 and earlier.
Distinctive features
Restores access to the WooCommerce Legacy REST API after it was removed from WooCommerce core. Preserves existing user keys and matches the legacy endpoints and behavior available in WooCommerce 8.9 and earlier.
CONTENT BOUNDARY
WooCommerce Legacy REST API capabilities and translation scope are documented separately.
The available evidence documents plugin functionality, but does not currently establish a specific visitor-facing translation surface.
Functional capability alone is not treated as evidence that a value should be translated.
LIMITATIONS & QA
Verification notes
- Not compatible with High-Performance Order Storage. It is intended for WooCommerce 9.0 and later, while WooCommerce 8.9 and earlier already include the Legacy REST API and are left unchanged.
COMMON QUESTIONS
WooCommerce Legacy REST API and REEID Translate FAQ.
What does WooCommerce Legacy REST API do according to the available plugin evidence?
WooCommerce Legacy REST API has 5 concrete capabilities documented from the currently available official plugin evidence. See the Plugin Intelligence section for the individual capabilities.
Is a REEID translation surface currently confirmed for WooCommerce Legacy REST API?
No specific visitor-facing content values are currently confirmed as an evidence-backed translation surface for this integration.
What would establish translation scope for WooCommerce Legacy REST API?
The evidence must identify concrete visitor-facing values such as labels, titles, descriptions, messages or other human-readable content that can be validated through the integration workflow.
RELATED GUIDES
Continue through the compatibility library.
INTEGRATION EVIDENCE
Evaluate WooCommerce Legacy REST API in a multilingual WordPress workflow.
REEID documents WooCommerce Legacy REST API functionality separately from evidence-backed translation support so compatibility claims remain specific and testable.
Translation scope will be published when concrete visitor-facing content is established by evidence.