Admin invalid request

Identifiers

Field	Value
Type URI	https://echo.labstack.com/pro/problems/admin-invalid-request
Code	admin_invalid_request
HTTP status	400

HTTP status	English title
400	Bad Request

When it occurs

The console or panel rejected a request parameter or action input. Causes include unknown or repeated parameters and malformed values. The console also uses this code when Config.Middleware returns HTTP 400.

Client handling

Correct the parameters as the view or action documents them, then send the request again. Sending it unchanged gives the same result.

Example response

If your application installs a custom handler, the body may differ.

HTTP/1.1 400 Bad Request
Content-Type: application/problem+json
Cache-Control: no-store

{
  "code": "admin_invalid_request",
  "detail": "",
  "status": 400,
  "title": "Bad Request",
  "type": "https://echo.labstack.com/pro/problems/admin-invalid-request"
}

Server correction

Validate application-generated parameters against the panel descriptor. Preserve the preview’s values when committing.

Response fields

Admin console

• code (string, always): The stable code above.
• detail (string, always): The console always sends detail. It is often empty and never contains the underlying error.
• status (integer, always): The HTTP status of the response.
• title (string, always): The HTTP status text, such as Conflict, unless the panel supplies its own title.
• type (string, always): The exact type URI above.

Headers:

• Cache-Control (always): no-store. The console sends it on every problem response, along with its usual security headers.

Notes:

• Fields are written in alphabetical order.
• The console rewrites every 404 response to admin_not_found with an empty detail.

Related behavior

See the admin console for access checks, action IDs and audit failures.