Skip to main content

​
HTTP Status Codes

StatusMeaning
200Successful read
202Execution accepted and started asynchronously
400Invalid request body or inputs
401Missing or invalid API key
403Access denied for this workspace or app
404App or execution not found
500Unexpected server-side failure

​
Common Error Cases

​
Invalid API key

{
  "error": "Invalid API key"
}
Action:
  • verify the key value
  • make sure the key has not been revoked
  • confirm you are using the correct environment

​
Missing API key

{
  "error": "Missing API key"
}
Action:
  • send x-api-key
  • or send Authorization: Bearer ...

​
Invalid inputs

{
  "error": "Invalid inputs",
  "details": [
    "\"Location\": invalid option \"Mars\". Must be one of: Studio, Urban, Park"
  ]
}
Action:
  • fetch app metadata again
  • validate input names and option labels before retrying

​
App not found

{
  "error": "App not found"
}
Action:
  • verify the appId
  • confirm the app is accessible to the workspace associated with your key

​
Execution not found

{
  "error": "Execution not found"
}
Action:
  • verify the executionId
  • confirm you are checking from the same workspace context that started the execution

​
Retry Guidance

Safe to retry:
  • transient 500 responses
  • network timeouts while fetching status
Usually do not retry unchanged:
  • 400 invalid inputs
  • 401 invalid API key
  • 403 access denied
  • 404 wrong app or execution ID

​
Support Checklist

If you need to debug an issue quickly, capture:
  • request path
  • app ID
  • execution ID
  • timestamp
  • top-level error message
  • output-level errors