Admin selection required
Identifiers
Section titled “Identifiers”| Field | Value |
|---|---|
| Type URI | https://echo.labstack.com/pro/problems/admin-selection-required |
| Code | admin_selection_required |
| HTTP status | 400 |
| HTTP status | English title |
|---|---|
| 400 | Bad Request |
When it occurs
Section titled “When it occurs”The console needs more selection input before it can read a view or prepare an action. No action ran.
Client handling
Section titled “Client handling”Fill in the selection fields requested by the panel, such as plan, limit or amount, and submit again. For an action, request a new preview before committing.
Example response
Section titled “Example response”If your application installs a custom handler, the body may differ.
HTTP/1.1 400 Bad RequestContent-Type: application/problem+jsonCache-Control: no-store
{ "code": "admin_selection_required", "detail": "", "status": 400, "title": "Bad Request", "type": "https://echo.labstack.com/pro/problems/admin-selection-required"}Server correction
Section titled “Server correction”Supply the selection fields requested by the panel, such as plan, limit or amount, then request a new preview before committing an action.
Response fields
Section titled “Response fields”Admin console
Section titled “Admin console”code(string, always): The stable code above.detail(string, always): The console always sendsdetail. 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 asConflict, 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_foundwith an emptydetail.
Related behavior
Section titled “Related behavior”See the admin console for access checks, action IDs and audit failures.