Errors

Documentation Index

Fetch the complete documentation index at: https://docs.uselamina.ai/llms.txt

Use this file to discover all available pages before exploring further.

​

Error Envelope

{
  "error": "Human-readable error message",
  "code": "AUTH_INVALID_KEY",
  "retryable": false,
  "requestId": "550e8400-e29b-41d4-a716-446655440000"
}

​

Error Codes

​

HTTP Status Codes

​

Interpreting 202 Accepted

• store the returned run ID
• call GET /v1/runs/{runId}/wait?timeout=60 (simplest)
• or poll GET /v1/runs/{runId} every 3-5 seconds
• or wait for your webhook callback

​

Common Error Cases

​

Authentication errors

{
  "error": "Missing API key",
  "code": "AUTH_MISSING_KEY",
  "retryable": false,
  "requestId": "abc-123"
}

• AUTH_MISSING_KEY: send x-api-key header or Authorization: Bearer ...
• AUTH_INVALID_KEY: verify the key value, check it has not been revoked, confirm correct environment
• AUTH_INVALID_CONTEXT: the key exists but is misconfigured — contact support

​

Invalid inputs

{
  "error": "Invalid inputs",
  "code": "VALIDATION_ERROR",
  "retryable": false,
  "requestId": "abc-123",
  "details": [
    {
      "param": "Mention Key Ingredients",
      "code": "missing_no_default",
      "message": "\"Mention Key Ingredients\" is required: no default is configured for this parameter."
    },
    {
      "param": "Location",
      "code": "invalid_option",
      "message": "\"Location\": invalid option \"Mars\". Must be one of: Studio, Urban, Park"
    }
  ]
}

1. Parse details[] and branch on code.
2. For missing_no_default: read the param field, look it up in your cached schema, and fill in a value.
3. For unknown_parameter: re-fetch GET /v1/apps/{appId} — your cached schema may be stale.
4. For invalid_option: read the message for the allowed option list and pick one.
5. For invalid_media or invalid_type: fix the value and retry.

​

Not found

{
  "error": "App not found",
  "code": "NOT_FOUND",
  "retryable": false,
  "requestId": "abc-123"
}

• verify the appId or runId
• confirm the resource is accessible to the workspace associated with your key

​

Rate limit exceeded

{
  "error": "Too many requests, please try again later",
  "code": "RATE_LIMITED",
  "retryable": true,
  "retryAfter": 60,
  "requestId": "abc-123"
}

• wait retryAfter seconds before retrying
• read RateLimit-Limit, RateLimit-Remaining, and RateLimit-Reset headers
• avoid tight polling loops; prefer webhooks or the wait endpoint for long-running executions

​

Current Rate Limit

​

Retry Guidance

• RATE_LIMITED — wait retryAfter seconds first
• INTERNAL_ERROR — transient server failure, use exponential backoff
• AUTH_FAILED — transient database error
• RESOURCE_UNAVAILABLE — service temporarily down
• Network timeouts while fetching status
• Idempotent reads (GET /v1/apps, GET /v1/runs/{id})

• VALIDATION_ERROR — fix the inputs first
• AUTH_MISSING_KEY / AUTH_INVALID_KEY — fix credentials
• FORBIDDEN — access denied, won’t change on retry
• NOT_FOUND — wrong ID

​

Support Checklist

• requestId from the error response
• code from the error response
• request path and method
• app ID or execution ID
• timestamp