For AI agents: a documentation index is available at the root level at /llms.txt and /llms-full.txt. Append /llms.txt to any URL for a page-level index, or .md for the markdown version of any page.
DiscordGet API Key
  • Getting Started
    • Overview
    • Quickstart
    • Errors
    • Pricing
  • Chat
    • Overview
    • Chat with Image, Video, and Audio
    • Function Calling
    • Models
  • Vision
    • Overview
    • Rate Limits
    • Pricing
    • MCP Server
    • Video Management
    • Video Group Management
    • Video Search
    • Video QA
    • Clip Generation
    • Metadata Tagging
    • Image Management
    • Image Search
  • Research
    • Overview
    • Streaming
    • Reasoning Steps
    • Web Search
    • Structured Output
    • Parallel Thinking
    • Best Practices
    • Errors
    • Examples
  • Speech
    • Overview
    • Audio Transcription
    • Speech Translation
    • Speech-to-Speech Translation
  • Resources
    • FAQs
    • Changelog
    • System Status
LogoLogo
DiscordGet API Key
On this page
  • API errors
  • Error Types and HTTP Status Codes
  • Request ID
Getting Started

Errors

Was this page helpful?
Previous

API Pricing

Next
Built with

API errors

Errors are returned as a JSON response with the following shape:

1{
2 "error": {
3 "type": "not_found_error",
4 "message": "Video not found",
5 "param": "video_id",
6 "details": [...]
7 }
8}
FieldTypeDescription
typestringError category for client-side handling (see table below)
messagestringHuman-readable explanation
param (optional)stringWhen present, indicates with request parameter caused the error
details (optional)arrayWhen present, provides additional information on request errors

Error Types and HTTP Status Codes

StatusError TypeClient Action
400validation_errorFix your request and retry
401authentication_errorEnsure that you’re using a valid Reka API key
404not_found_errorResource not found
429rate_limit_errorWait until your rate limit is restored and retry, or upgrade your API tier for higher limits
500server_errorRetry with backoff. If this persists, contact Reka at contact@reka.ai

Request ID

Every response includes an X-Request-ID header for log correlation:

X-Request-ID: a1b2c3d4e5f6...

This is not duplicated in the response body. Please include this ID when reporting issues.