GetRouterDocs
  • English

    • Base URL and Endpoints

    For OpenAI-compatible SDKs and tools, use this Base URL:

    https://getrouter.ai/v1

    For direct HTTP requests, append the endpoint path shown below.

    Common endpoints

    CapabilityMethodFull endpoint
    List OpenAI-format modelsGEThttps://getrouter.ai/v1/models
    Chat CompletionsPOSThttps://getrouter.ai/v1/chat/completions
    ResponsesPOSThttps://getrouter.ai/v1/responses
    Compact Responses contextPOSThttps://getrouter.ai/v1/responses/compact
    EmbeddingsPOSThttps://getrouter.ai/v1/embeddings
    Image generationPOSThttps://getrouter.ai/v1/images/generations
    Image editingPOSThttps://getrouter.ai/v1/images/edits
    Audio transcriptionPOSThttps://getrouter.ai/v1/audio/transcriptions
    Audio translationPOSThttps://getrouter.ai/v1/audio/translations
    Text to speechPOSThttps://getrouter.ai/v1/audio/speech
    Video task creationPOSThttps://getrouter.ai/v1/videos
    Video task statusGEThttps://getrouter.ai/v1/videos/{task_id}
    RerankPOSThttps://getrouter.ai/v1/rerank
    Claude MessagesPOSThttps://getrouter.ai/v1/messages
    Gemini-format modelsGEThttps://getrouter.ai/v1beta/models
    Gemini generateContentPOSThttps://getrouter.ai/v1beta/models/{model}:generateContent

    Base URL versus full endpoint

    SDKs usually ask for a Base URL and append the operation path themselves:

    Base URL entered in an OpenAI SDK:
https://getrouter.ai/v1

SDK sends the request to:
https://getrouter.ai/v1/chat/completions

    Some tools ask for a complete endpoint instead. Read the field label and the integration guide before adding /chat/completions, /responses, or /messages manually.

    Avoid duplicated paths

    A duplicated path is a common cause of 404 Not Found errors.

    Correct OpenAI Base URL:
https://getrouter.ai/v1

Incorrect when the tool already appends /v1:
https://getrouter.ai/v1/v1

Incorrect when the tool already appends /chat/completions:
https://getrouter.ai/v1/chat/completions/chat/completions
    Tip

    If a tool has separate fields for API Host, API Version, and Endpoint, follow that tool's dedicated integration guide rather than guessing which path it appends.

    Authentication

    Unless an integration guide states otherwise, send:

    Authorization: Bearer YOUR_API_KEY
Content-Type: application/json

    Multipart endpoints, such as audio transcription and video creation, set their own Content-Type boundary automatically when you use curl -F or an SDK.

    Next steps