Libraries tagged by response errors

Some features to work with error handling in Laravel codes

Go to Download

A Symfony bundle that implements application/problem+json to give meaning to api response errors

Go to Download

Framework-agnostic core contracts, HMAC security utilities, and API response/error standards for SIPRO internal API.

Go to Download

A comprehensive Laravel package for integrating with Beem Africa's API services including SMS, OTP, Airtime, USSD, Voice, and Insights. Provides a clean, expressive interface with Laravel Notifications support, typed responses, and robust error handling.

Go to Download

PHP middleware that returns a json formatted response in case of error

Go to Download

Simple wrapper for the illuminate support, http response, request, validation, zttp, cache, encryption, blade templating and whoops error handler for WordPress

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

Efficient Laravel error handling with custom exception handling, logging, and response formatting.

Go to Download

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

Go to Download

Response package with JSON API standard responses, error handling, and response helpers

Go to Download

is a PHP package designed to simplify and standardize API response management in your applications. With this package, you can easily send success responses, error responses, and validation error responses in a consistent and structured format. This package aims to enhance the efficiency and ease of API development

Go to Download

A Laravel package to standardize API responses, errors, and validation outputs across Laravel applications

Go to Download

Library for standardization of error messages and success of api json.

Go to Download

Go to Download

Format generic JSON API errors for Laravel

Go to Download