hammadev2

Stop receiving 50+ fields when your app needs 3. ShopMobi – API Optimizer for WooCommerce gives your store GraphQL-like flexibility over REST — plus login, password reset, and Stripe payments out of the box.
Built for developers creating mobile apps, Flutter apps, React Native apps, or any headless WooCommerce frontend.
<h4>Field Filtering</h4>
Apply field filtering to any WooCommerce REST API response. No changes required on the server side — clients request only what they need.
Via request header (recommended for apps): 
 X-WC-Fields: id,name,price,images
Via query parameter: 
 ?fields=id,name,price,images
Exclude specific fields: 
 X-WC-Except: meta_data,description or <code>?except_fields=meta_data</code>
When both header and query parameter are provided, the header takes priority. The plugin applies filtering after WooCommerce builds the full response, so all existing WooCommerce hooks and permissions remain intact.
<h4>Custom REST Endpoints</h4>
The plugin registers the following custom endpoints under the <code>shopmobi/v1</code> namespace:
Authentication
<ul>
<li><code>POST /wp-json/shopmobi/v1/users/login</code> — Login with username and password</li>
<li><code>POST /wp-json/shopmobi/v1/users/register</code> — Register a new customer account</li>
<li><code>POST /wp-json/shopmobi/v1/users/update-profile</code> — Update first name, last name, and phone (requires login)</li>
</ul>
Password Reset
<ul>
<li><code>POST /wp-json/shopmobi/v1/users/reset-password/generate</code> — Send a password reset link to the user’s email (WordPress native flow)</li>
<li><code>POST /wp-json/shopmobi/v1/users/reset-password/verify</code> — Verify the reset key and set a new password</li>
</ul>
Store Information
<ul>
<li><code>GET /wp-json/shopmobi/v1/general-settings</code> — Country, currency, and active payment gateways (public)</li>
<li><code>GET /wp-json/shopmobi/v1/store-location</code> — Store address and location (requires login)</li>
<li><code>GET /wp-json/shopmobi/v1/payment-gateways</code> — Available payment gateways</li>
</ul>
Payments
<ul>
<li><code>POST /wp-json/shopmobi/v1/stripe-payment</code> — Create a Stripe PaymentIntent and EphemeralKey for mobile checkout (requires login)</li>
</ul>
<h4>Product Variation Enhancement</h4>
Variation responses are enriched automatically. Raw variation IDs in product responses are replaced with full objects including:
<ul>
<li>Pricing (regular price, sale price, on_sale flag)</li>
<li>SKU and stock quantity</li>
<li>Stock status</li>
<li>Attributes with labels and slugs</li>
<li>Variation image URL</li>
</ul>
<h4>Third-Party Services</h4>
This plugin optionally integrates with Stripe (https://stripe.com) for payment processing. The Stripe integration is inactive until you provide API keys under WooCommerce > API Optimizer.
When the <code>/shopmobi/v1/stripe-payment</code> endpoint is called, payment data (amount, currency, Stripe customer ID) is sent directly to Stripe’s servers. No payment data passes through ShopMobi or any other third party.
<ul>
<li>Stripe Privacy Policy: https://stripe.com/privacy</li>
<li>Stripe Terms of Service: https://stripe.com/legal</li>
</ul>
Your Stripe API keys are stored in your WordPress database and are never shared with the plugin author.
<h3>Privacy Policy</h3>
This plugin stores data in your own WordPress database only:
<ul>
<li>Stripe Customer IDs (<code>stripe_cust_id</code> user meta) — created when a user makes a Stripe payment. Stored locally and shared only with Stripe to identify returning customers.</li>
<li>Password Reset Keys — handled entirely by WordPress core (<code>get_password_reset_key()</code> / <code>reset_password()</code>). No custom data is stored in user meta by this plugin.</li>
</ul>
This plugin does not track users, send analytics, or transmit any personal data to ShopMobi or any third party, except for payment data sent directly to Stripe when the Stripe endpoint is used.
For Stripe’s data handling practices, see https://stripe.com/privacy.

ShopMobi – API Optimizer for WooCommerce

ShopMobi reduces WooCommerce REST API response size with field filtering and adds ready-made endpoints for auth, Stripe payments, and store settings.

Daniel Bachhuber

Ryan McCue

Joe Hoyle

Jonny Harris

Rachel Baker

This plugin uses the OAuth 1.0a protocol to allow delegated authorization; that is, to allow applications to access a site using a set of secondary credentials. This allows server administrators to control which applications can access the site, as well as allowing users to control which applications have access to their data.
This plugin only supports WordPress >= 4.4.
The latest stable version is also available from the <a href="https://wordpress.org/plugins/rest-api-oauth1/" rel="ugc">WordPress Plugin Directory</a>.
<h3>New to OAuth</h3>
We strongly recommend you use an existing OAuth library. You’ll be best off if you understand the authorization process, but leave the actual implementation to well-tested libraries, as there are a lot of edge cases.
Start reading from <a href="docs/introduction/README.md" rel="nofollow ugc">the Introduction</a> to get started!
<h3>For OAuth Veterans</h3>
If you already know how to use OAuth, here’s the lowdown:
<ul>
<li>The plugin uses OAuth 1.0a in</li>
<li>We use the three-legged flow</li>
<li>To find the REST API index, apply the <a href="http://v2.wp-api.org/guide/discovery/" rel="nofollow ugc">API autodiscovery process</a></li>
<li>The endpoints for the OAuth process are available in the REST API index: check for <code>$.authentication.oauth1</code> in the index data.
<ul>
<li>The temporary credentials (request token) endpoint is <code>$.authentication.oauth1.request</code> (typically <code>/oauth1/request</code>)</li>
<li>The authorization endpoint is <code>$.authentication.oauth1.authorize</code> (typically <code>/oauth1/authorize</code>)</li>
<li>The token exchange (access token) endpoint is <code>$.authentication.oauth1.access</code> (typically <code>/oauth1/access</code>)</li>
</ul>
</li>
<li>Your callback URL must match the registered callback URL for the application in the scheme, authority (user/password) host, port, and path sections. (Subpaths are not allowed.)</li>
<li>The only signature method supported is HMAC-SHA1.</li>
<li>OAuth parameters are supported in the Authorization header, query (GET) parameters, or request body (POST) parameters (if encoded as <code>application/x-www-form-urlencoded</code>). OAuth parameters are not supported in JSON data.</li>
</ul>

WP REST API – OAuth 1.0a Server

Hello, I have made an adapter for Parse Server under Node.js with which you can link the login of any installation of wordpress in Parse Server, for that I have used your plugin, which is the one that gives us access_token and allows us to verify the authenticity Of the user registered in the server.

https://github.com/enriquecerda/parse-server-wordpress-login

Links with Parse-server Node.js

Got this working after some good amount of work! Thanks for bringing this and making API calls secure.

Worked like a charm!

Really Useful And Good Plugin
But Please
1- Reply on The Support Forum
2- Update it To Work Good With Last WordPress Verison
3 – No Clear Docs
4 - not work with localhost

Good But

Connect applications to your WordPress site without ever giving away your password.

ShopMobi – API Optimizer for WooCommerce vs WP REST API – OAuth 1.0a Server