Libraries tagged by api exceptions
harrisonratcliffe/laravel-api-responses
132 Downloads
A Laravel package to easily handle API responses and exceptions
wollanup/php-api-rest-interfaces
1674 Downloads
Interfaces and Exceptions for php-api-rest project implementation
mattjanssen/api-response-bundle
9598 Downloads
Symfony bundle for transforming controller action returns and exceptions into JSON API responses
m-hidayatullahh/laravel-api-kit
55 Downloads
Standardized API response envelope and global exception handling for Laravel 10 & 11.
phil/api-contract-bundle
4 Downloads
Both sides of an unversioned HTTP API contract for Symfony, on phil/api-contract and phil/idempotency: exceptions as problem details, #[Idempotent] controllers with keys in Doctrine or a cache pool, #[DeprecatedEndpoint] controllers, the deprecations of called APIs recorded and checked in CI, and its OpenAPI document checked by level
stackmasteraliza/laravel-api-response
57 Downloads
A clean, fluent, and consistent API response builder for Laravel 10/11/12. Features standardized JSON responses, automatic pagination metadata, built-in exception handling, validation error formatting, and a convenient trait for controllers.
php-dev-umesh/laravel-api-response
95 Downloads
Comprehensive API response builder for Laravel with success, error, pagination, streaming, download responses, auto-translation, and exception handling.
patricksavalle/slim-rest-api
1404 Downloads
Production-grade REST-API App-class for PHP SLIM, in production on https://zaplog.pro (https://api.zaplog.pro/v1)
darvis/laravel-api-key-alert
18 Downloads
Get an email the moment an API key stops working in Laravel: detects rejected keys in Http client calls, reported exceptions, wrapped calls and a daily check, for Google, OpenAI, Anthropic, Mollie and any API you add. Also reminds you daily while APP_DEBUG or APP_ENV is wrong on a server.
chiron/http-exceptions
2775 Downloads
Exception classes for Http Exception.
osm/easy-rest-bundle
1451 Downloads
Simple and lightweight bundle provides JSON based request / response and exception handling support to develop RESTful API's with Symfony.
thecyrilcril/imagekit-laravel-client
303 Downloads
A Laravel-native ImageKit API client built on Illuminate\Http\Client: typed requests, typed results, typed exceptions.
processhub/laravel-logs
452 Downloads
ProcessHub centralized logging for Laravel applications — ships logs, exceptions, and deploy markers to ProcessHub's /api/ingest endpoints
leibbrand-development/php-docker-client
33 Downloads
The Engine API is an HTTP API served by Docker Engine. It is the API the Docker client uses to communicate with the Engine, so everything the Docker client can do can be done with the API. Most of the client's commands map directly to API endpoints (e.g. `docker ps` is `GET /containers/json`). The notable exception is running containers, which consists of several API calls. # Errors The API uses standard HTTP status codes to indicate the success or failure of the API call. The body of the response will be JSON in the following format: ``` { "message": "page not found" } ``` # Versioning The API is usually changed in each release, so API calls are versioned to ensure that clients don't break. To lock to a specific version of the API, you prefix the URL with its version, for example, call `/v1.30/info` to use the v1.30 version of the `/info` endpoint. If the API version specified in the URL is not supported by the daemon, a HTTP `400 Bad Request` error message is returned. If you omit the version-prefix, the current version of the API (v1.41) is used. For example, calling `/info` is the same as calling `/v1.41/info`. Using the API without a version-prefix is deprecated and will be removed in a future release. Engine releases in the near future should support this version of the API, so your client will continue to work even if it is talking to a newer Engine. The API uses an open schema model, which means server may add extra properties to responses. Likewise, the server will ignore any extra query parameters and request body properties. When you write clients, you need to ignore additional properties in responses to ensure they do not break when talking to newer daemons. # Authentication Authentication for registries is handled client side. The client has to send authentication details to various endpoints that need to communicate with registries, such as `POST /images/(name)/push`. These are sent as `X-Registry-Auth` header as a [base64url encoded](https://tools.ietf.org/html/rfc4648#section-5) (JSON) string with the following structure: ``` { "username": "string", "password": "string", "email": "string", "serveraddress": "string" } ``` The `serveraddress` is a domain/IP without a protocol. Throughout this structure, double quotes are required. If you have already got an identity token from the [`/auth` endpoint](#operation/SystemAuth), you can just pass this instead of credentials: ``` { "identitytoken": "9cbaf023786cd7..." } ```
iafilin/eloquenthttpadapter
521 Downloads
EloquentHttpAdapter is a Laravel package that allows you to work with RESTful API data using an Eloquent-like syntax with HttpModel abstract class, interfaces, and custom exceptions.