Libraries tagged by api problem

RFC7807 Api Problem

Go to Download

API Problem implementation

Go to Download

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

Go to Download

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

Go to Download

A bundle that formats the JSON api problem

Go to Download

Standardize error responses in API applications

Go to Download

BayWa r.e. Laminas API Problem handling

Go to Download

API Problems according to RFC 7807

Go to Download

Implements the Libero API error standard

Go to Download

A starting point for a Zana JSON API: modules, bearer tokens, problem JSON errors, a database, and instructions for AI coding agents

Go to Download

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

The lockally control plane lets integrators and direct customers manage everything except actual mail data flow (which uses standard JMAP / IMAP / SMTP-submission against the data plane endpoints). **Authentication.** All `/v1/_*` endpoints require a Bearer API key in the `Authorization` header. Keys are formatted `lk_live__`, or `lk_test_` for a test key. Create keys in the dashboard, or with `POST /v1/api-keys` using a key that holds `tenant:admin`. The key's plan is checked on every request, so a key stops working if the account moves to a plan without API access, and works again if it moves back. **Errors.** Failures return [RFC 9457](https://www.rfc-editor.org/rfc/rfc9457) `application/problem+json` documents. **Scopes.** Each endpoint requires a specific scope on the presented key. Insufficient scope returns `403` with the required scope name in `detail`.

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