Libraries tagged by http-status-code

Constants enumerating the HTTP Status Codes. Based on the HTTP Status Code Registry.

Go to Download

A simple package to send HTTP response headers from your PHP application

Go to Download

Truly minimalistic and self-contained package to handle HTTP statuses and relevant description messages

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

Utility to check if a HTTP status code is present in a given range.

Go to Download

Small PHP library for easily accessing HTTP Status Codes.

Go to Download

HTTP Status Codes and Exceptions

Go to Download

PHP HTTP Status Code Exceptions

Go to Download

A PHP trait which defines all standard HTTP status codes.

Go to Download

PHP Class that contains HTTP Status Codes

Go to Download

A simple class to return correct status codes for http responses

Go to Download

HTTP Status Codes library

Go to Download

Helper to get HTTP status code by using common name

Go to Download

The "HTTP Status Code Abstraction" project is a PHP 8-based initiative aimed at simplifying the management and usage of HTTP status codes by introducing ENUM support. HTTP status codes are integral to web development, providing vital information about the success or failure of HTTP requests and responses. However, managing and referencing these status codes in a clear and organized manner can often be challenging. This project seeks to address this challenge by leveraging PHP 8's ENUM feature.

Go to Download

List constants for http status codes

Go to Download