Error Codes

This page documents all error codes returned by the Transcript LOL API. Understanding these errors will help you handle failures gracefully in your application.

Error Response Format

All error responses follow a consistent JSON structure:

{
  "error": {
    "code": "ERROR_CODE",
    "message": "Human readable error message"
  }
}

HTTP Status Codes

400 - Bad Request

Invalid input

Possible Causes:

• Missing required fields in the request body
• Invalid field values or data types
• Malformed JSON in the request body

Resolution: Check the API documentation for required fields and correct data types. Validate your JSON payload before sending.

---

401 - Unauthorized

Authentication failed

Possible Causes:

• Missing x-api-key header
• Invalid or expired API key
• API key has been revoked

Resolution: Ensure you include a valid x-api-key header. Generate a new API key from the Integrations page if needed.

---

402 - Payment Required

Insufficient credits or need payment

Possible Causes:

• Insufficient credits in your account
• Subscription has expired
• Feature requires a paid plan

Resolution: Add credits to your account or upgrade your subscription plan from the billing page.

---

403 - Forbidden

You don't have access

Possible Causes:

• Attempting to access a resource you don't own
• Insufficient permissions for the requested action
• Resource belongs to a different workspace

Resolution: Verify you have the correct permissions and are accessing resources within your workspace.

---

404 - Not Found

Not found or don't have access

Possible Causes:

• The requested resource does not exist
• Resource has been deleted
• Incorrect resource ID in the URL

Resolution: Verify the resource ID is correct. The resource may have been deleted or you may not have access to it.

---

500 - Internal Server Error

Unexpected error

Possible Causes:

• Unexpected server error
• Temporary service disruption
• Processing error on our end

Resolution: Retry the request after a few seconds. If the error persists, contact support.

---

Best Practices

• Always check the status code - Don't assume requests succeed
• Implement retry logic - For 5xx errors, implement exponential backoff
• Log errors - Store error responses for debugging
• Handle rate limits - Respect 429 responses and slow down requests