WooCommerce Legacy REST API vs WPGraphQL

The Legacy REST API will no longer part of WooCommerce as of version 9.0. This plugin restores the full functionality of the removed Legacy REST API code in WooCommerce 9.0 and later versions. For all intents and purposes, having this plugin installed and active in WooCommerce 9.0 and newer versions is equivalent to enabling the Legacy REST API in WooCommerce 8.9 and older versions (via WooCommerce – Settings – Advanced – Legacy API). All the endpoints work the same way, and existing user keys also continue working. On the other hand, installing this plugin together with WooCommerce 8.9 or an older version is safe: the plugin detects that the Legacy REST API is still part of WooCommerce and doesn’t initialize itself as to not interfere with the built-in code. Please note that the Legacy REST API is not compatible with High-Performance Order Storage. Upgrading the code that relies on the Legacy REST API to use the current WooCommerce REST API instead is highly recommended.

WPGraphQL is a free, open-source WordPress plugin that provides an extendable GraphQL schema and API for any WordPress site. Get Started Install WPGraphQL: wp plugin install wp-graphql --activate Try it out: Live Demo Read the Quick Start Guide. Join the Community on Discord and Star the Repo! Key Features Flexible API: Query posts, pages, custom post types, taxonomies, users, and more. Extendable Schema: Easily add functionality with WPGraphQL’s API, enabling custom integrations. Compatible with Modern Frameworks: Works seamlessly with Next.js, Astro, SvelteKit, and more. Optimized Performance: Fetch exactly the data you need in a single query. Boost performance with WPGraphQL Smart Cache. WPGraphQL is becoming a Canonical Plugin on WordPress.org, ensuring long-term support and a growing community of users and contributors. Upgrading It is recommended that anytime you want to update WPGraphQL that you get familiar with what’s changed in the release. WPGraphQL publishes release notes on Github. WPGraphQL has been following Semver practices for a few years. We will continue to follow Semver and let version numbers communicate meaning. The summary of Semver versioning is as follows: MAJOR version when you make incompatible API changes, MINOR version when you add functionality in a backwards compatible manner, and PATCH version when you make backwards compatible bug fixes. You can read more about the details of Semver at semver.org Privacy Policy WPGraphQL uses Appsero SDK to collect some telemetry data upon user’s confirmation. This helps us to troubleshoot problems faster and make product improvements. Appsero SDK does not gather any data by default. The SDK starts gathering basic telemetry data only when a user allows it via the admin notice. When you opt in, each telemetry request is sent to Appsero and a duplicate is sent in a non-blocking request to WPGraphQL-operated infrastructure at https://telemetry.wpgraphql.com (the same categories of data as described for Appsero below). Learn more about how Appsero collects and uses this data.