Libraries tagged by api exceptions

Hyperf unified API JSON responses with business codes, exception handler and api_response() helper

Go to Download

A Laravel package for consistent and configurable API responses with built-in exception handling.

Go to Download

A minimal, reusable REST API toolkit for Laravel: consistent JSON responses, a typed exception hierarchy, and base API model/controller.

Go to Download

A pluggable Laravel package for unified REST API responses with Response Macros and exception handling

Go to Download

Laravel exception handler build specifically for APIs.

Go to Download

The Package Exception Notification through Telegram Bot API.

Go to Download

Api response allows you to handle exceptions simply and custom.

Go to Download

Exception handler for The Ultra Fast API

Go to Download

Advanced API error handling for Laravel with multiple format support, smart debugging, and developer-friendly features

Go to Download

Use the OpenAI API together with Laravel Ignition's Suggestions to show AI-powered fixes for errors in your Laravel application.

Go to Download

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.43) is used. For example, calling `/info` is the same as calling `/v1.43/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..." } ```

Go to Download

A laravel package for easily build json api response.

Go to Download

Centralized, enum-based API error codes for Laravel — frontend-safe, RFC 7807 compatible, Swagger-ready, with TypeScript export, Sentry integration, and request tracing.

Go to Download

Use the OpenAI API together with Laravel Ignition's Suggestions to show AI-powered fixes for errors in wordpress/sage.

Go to Download

Handle all exception and save in db

Go to Download