Build a fully custom headless storefront - your own web app, mobile app, or POS - against a single OE Commerce store. Every endpoint below is namespaced under `/api/v1/store/...`. Building admin/back-office tooling instead? See [/docs/admin](/docs/admin). New here? [/guides/store](/guides/store) walks through getting a key, the anonymous cart session, and calling your first endpoints step by step - this page is the field-level reference to come back to afterward. ## Getting Started 1. Click the **Authorize** button at the top of this page. 2. Provide credentials: - **X-Commerce-Key** (always required) - your store's Store Access Key from Backoffice > Settings > Application APIs. `pk_store_...` (publishable) is safe for browser/mobile code; `sk_store_...` (secret) is server-to-server only and is rejected outright if a browser Origin header is present. - **Bearer** (only for endpoints acting on a specific customer - Account, Orders, Wishlists, etc.) - the token from **Auth > register** or **Auth > login**. Once authorized, you can explore and test all available endpoints directly from this interface. ## Anonymous Carts A guest cart is tracked by an `X-Session-Ref` header, not a cookie - the server generates one on your first request and echoes it back on every response after. Keep sending back whatever value you last received. Logging in carries that same cart forward onto the customer's account automatically, with no separate merge step. ## Errors Failures use RFC 9457 Problem Details (`application/problem+json`) with a stable `code` field for programmatic handling, e.g. `store_key_invalid`, `store_key_revoked`, `store_key_scope_denied`, `rate_limited`. A rejected *business* action (e.g. adding fewer than a product's minimum order quantity to the cart) instead comes back as HTTP 200 with `"success": false` and a human-readable `message` - always check `success` in the body, not just the HTTP status code. ## Rate Limits Requests are limited per Store Access Key (200/minute). The credential-stuffing surface (register/login/forgot-password/reset-password) is limited more tightly per caller IP (10 per 5 minutes). A 429 response includes a `Retry-After` header.

Go to Download

noglitchyo/dealdoh-client

2 Favers
7 Downloads

A DNS proxy client to make/forward DNS query via HTTP & CLI with different protocols.

Go to Download

ngdot/contao-changenewsmore

0 Favers
110 Downloads

This extension makes it possible to replace 'Read more ...' with an individual text. Works for all forwarding destinations!

Go to Download

ngdot/contao-changeeventsmore

0 Favers
57 Downloads

This extension makes it possible to replace 'Read more ...' with an individual text. Works for all forwarding destinations!

Go to Download

mouf/utils.log.filter-logger

0 Favers
5 Downloads

This package contains a class that acts as a logger. It purpose is to apply a filter on logs and forward the logs to another logger that will take care of storing the log.

Go to Download

monosize/soap-proxy

0 Favers
171 Downloads

A secure PHP-based SOAP proxy that authenticates and forwards SOAP requests to a target server

Go to Download

mitinsany/cryptoapi-client-php

0 Favers
2 Downloads

Crypto APIs is a complex and innovative infrastructure layer that radically simplifies the development of any Blockchain and Crypto related applications. Organized around REST, Crypto APIs can assist both novice Bitcoin/Ethereum enthusiasts and crypto experts with the development of their blockchain applications. Crypto APIs provides unified endpoints and data, raw data, automatic tokens and coins forwardings, callback functionalities, and much more.

Go to Download