Libraries tagged by api problem

way to respect Problem Details for HTTP APIs RFC (http://tools.ietf.org/html/draft-nottingham-http-problem-03)

Go to Download

Problem Details for PSR-7 HTTP APIs

Go to Download

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

Laravel API Resources supercharged to get rid of N+1 problems.

Go to Download

Exception classes for Http Exception.

Go to Download

catch all Symfony 3.3 or newer errors and convert it to problem json RFC7807 response

Go to Download

catch all Symfony errors and convert it to problem json RFC7807 response

Go to Download

API Problem implementation

Go to Download

RFC 9457 Problem Details for Yii3 and any PSR-7/PSR-15 application

Go to Download

ZF2 Module providing API-Problem assets and rendering

Go to Download

A Symfony compatible response for the IETF Problem Details for HTTP APIs RFC

Go to Download

API Problems according to RFC 7807

Go to Download

RFC7807 Problem details integration for Symfony

Go to Download

Integration between crell/api-problem and the Symfony framework

Go to Download

Api Client Abstraction Layer that suggest solution to solve general api call problems.

Go to Download