Invalid request

Identifiers

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

HTTP status	English title
400	Invalid quota administration request

When it occurs

A quota administration route rejected its input. Causes include unknown or repeated query parameters, an invalid period, or a body other than one JSON object of at most 64 KiB sent as application/json.

Client handling

detail names the field, the reason and a fix. Correct the request and send it 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": "invalid_request",
  "status": 400,
  "title": "Invalid quota administration request",
  "type": "https://echo.labstack.com/pro/problems/invalid-request",
  "violated-policies": [
    "requests"
  ]
}

Server correction

Validate quota administration parameters, including plan, partition and credit operation ID. Do not use this code for your application’s unrelated 400 responses.

Response fields

Quota administration routes

• code (string, always): The stable code above.
• type (string, always): The exact type URI above.
• title (string, always): English title. Quota administration routes use their own titles for some codes.
• status (integer, always): The HTTP status of the response.
• detail (string, optional): Human-readable explanation, omitted when empty. Its wording is not a stable format.
• violated-policies (array, always): IDs of the limits involved: [] when there are none, never null.

Headers:

• Cache-Control (always): no-store on every administration response.

Notes:

• Quota administration rejected the request.

Related behavior

See quota for plans, credit adjustments and usage.