Salesforce Commerce Cloud OCAPI Proxy
Empower Commerce with OCAPI Proxy: Seamless Integration, Infinite Possibilities!
Free3,949 impressions#170 of its week
A Node.js proxy that forwards requests to a Salesforce Commerce Cloud OCAPI instance, handling CORS for mobile and browser apps.
- for
- Developers integrating or testing SFCC OCAPI in mobile/web applications.
- pricing
- free
- license
- open source
Key features
- Configurable proxy — Edit config.json to set server, site_id, client_id, ports and optional analytics.
- CORS bypass — Routes OCAPI calls through the proxy to avoid cross-origin restrictions.
- Built-in UI — Optional web UI (port_ui) for testing requests and viewing responses.
- Logging — Generates log files in a logs directory for request tracing.
- Universal Analytics support — Sends proxy usage events to Google Analytics when a UA ID is provided.
- Rate limiting options — Configurable rate_limit and max settings to control request volume per IP.
Use cases
- Testing third-party apps that consume SFCC OCAPI without CORS issues.
- Developing mobile applications that need to call OCAPI securely.
- Debugging OCAPI responses via the built-in web UI.
- Running automated API tests with Postman against a local proxy.
Salesforce Commerce Cloud OCAPI Proxy FAQ
What does the proxy actually do?+
It forwards OCAPI requests from your local machine to a Salesforce Commerce Cloud sandbox, handling CORS and optional analytics.
Do I need a Salesforce Commerce Cloud account?+
Yes, you need a sandbox configured for OCAPI access.
Can I disable the UI?+
Yes, set the UI configuration to disabled in config.json.
How are errors returned?+
If the SFCC instance is reachable, errors are returned in JSON format to aid debugging.
Is there rate limiting?+
Optional rate_limit and max settings let you limit requests per IP over a configurable window.
Summarized by DevHunt from npmjs.com · Oct 4, 2026. Details may change; check the official site.
