invalid_input

{
  "meta": {
    "requestId": "req_2c9a0jf23l4k567"
  },
  "error": {
    "detail": "Metadata is too large: it must be at most 1.0 MB, but is 1.4 MB.",
    "status": 400,
    "title": "Bad Request",
    "type": "/errors/unkey/application/invalid_input",
    "errors": []
  }
}

​

Likely causes

• A required field is missing, or a field has the wrong type, an unknown enum value, or is too long. The errors array lists each problem, and detail reads like POST request body for '/v2/keys.createKey' failed to validate schema.
• The Authorization header is missing.
• A value breaks a rule the endpoint checks, such as a size limit on meta or environment variable values, a domain that isn’t a fully qualified name or is a public suffix, an image reference we can’t parse, or rate limit and credit settings that contradict each other. Here errors is empty and detail explains.

​

How to fix

1. If errors has entries, fix each one. location is the path that failed (such as /required) and message says why.
2. Otherwise, follow the rule in detail. Size errors show both the limit and your value, so trim to the limit.
3. For domains, send a bare host name such as api.acme.com, with no scheme, port, or path.
4. For images, send a full reference such as ghcr.io/acme/app:1.2.3.

​

Related errors

• err:unkey:application:invalid_environment_settings: the environment’s settings, not your request, block a deployment.
• err:user:bad_request:request_body_too_large: the whole body exceeded the size cap.
• err:user:bad_request:permissions_query_syntax_error: a keys.verifyKey permissions query couldn’t be parsed.