To use RutaAPI with Open WebUI, add an OpenAI-compatible connection, set the API URL to https://api.rutaapi.com/v1, paste a RutaAPI API key, and verify that /v1/models returns available models. If Open WebUI does not auto-detect models, add model IDs copied from /v1/models. The API key, URL and model IDs must all belong to the same provider.
Before you start
You need a RutaAPI account, a prepaid credit pack, and an API key. Make sure your account has credits before making requests — requests without sufficient credits will return a 401 or 403 error.
What Open WebUI asks for Open WebUI supports adding OpenAI-compatible provider connections. Most users configure this through Admin Settings → Connections → OpenAI. Open WebUI typically asks for an API URL, an API key, and optionally a list of model IDs. All three values must belong to the same provider — using a URL from one platform with an API key from another will result in errors.
What OpenAI-compatible means in Open WebUI OpenAI-compatible in Open WebUI means the provider uses the same request/response format as the official OpenAI API. This includes a /v1/chat/completions endpoint, Bearer token authentication, and a /v1/models endpoint for listing available models. RutaAPI uses this format, which allows Open WebUI to connect without needing a custom integration.
What API URL to use for RutaAPI The API URL tells Open WebUI where to send requests. The correct RutaAPI API URL is <strong>https://api.rutaapi.com/v1</strong>. This is the OpenAI-compatible API root — it ends in /v1 and points to the API gateway, not the marketing site, dashboard or a direct endpoint path.
What API key to use The API key is the secret token that identifies your RutaAPI account. Paste your RutaAPI API key where Open WebUI asks for an API key. It must match the API URL — using a key from one provider with a URL from another will cause a 401 error.
What model IDs mean Model IDs are identifiers that tell Open WebUI which AI models are available in your account. If Open WebUI auto-detects models from /v1/models, you may not need to add them manually. If auto-detection does not work, copy model IDs from the /v1/models response and add them to the Model IDs field in Open WebUI. Do not guess model IDs — identifiers differ between providers.
Open WebUI version caveat Open WebUI UI labels, provider settings and connection options can change by version. Official Open WebUI documentation describes adding OpenAI-compatible provider connections through Admin Settings → Connections → OpenAI, but users should verify the current UI and behavior in their installed version before following any specific steps.
RutaAPI disclaimer RutaAPI is an OpenAI-compatible API gateway. It is not an official Open WebUI, OpenAI, Anthropic, Google or Microsoft service. Model availability and rates depend on your account configuration and upstream providers.
How to start with RutaAPI
Step 1 — Create a RutaAPI account
Register at app.rutaapi.com. No credit card is required to sign up.
Step 2 — Add prepaid credits
Purchase a credit pack from the billing section. Credits are added immediately after payment. Requests without sufficient credits return 401 or 403.
Step 3 — Create an API key
Go to the Tokens section and create a new key. Copy it right away — it is shown only once at creation.
Security: Never paste your full API key into screenshots or shared scripts. If exposed, rotate it immediately from the dashboard.
Step 4 — Verify /v1/models
Before configuring Open WebUI, confirm the key works by calling /v1/models:
A 200 response with a model list means the key is valid. A 401 response means the key is wrong or revoked.
curl https://api.rutaapi.com/v1/models \
-H "Authorization: Bearer YOUR_RUTAAPI_KEY"Step 5 — Copy model IDs
Use one or more model id values from the /v1/models response. These are the IDs you will add to Open WebUI if auto-detection does not work.
Copy the exact id strings. Model IDs differ between providers — do not guess.
Step 6 — Add Open WebUI connection
In Open WebUI, look for Admin Settings → Connections → OpenAI, then add an OpenAI-compatible connection if your version supports it. Enter:
Paste your RutaAPI API key where the provider expects an API key. Do not promise exact UI labels because Open WebUI changes over time — verify the current connection flow in your installed version.
https://api.rutaapi.com/v1Step 7 — Add model IDs if needed
If Open WebUI does not auto-detect models from /v1/models, look for a Model IDs field in the connection settings and add the model IDs you copied from Step 5.
If auto-detection works, you may not need to add model IDs manually. Skip this step if models appear automatically.
Step 8 — Send a small test request
Before starting a chat session, confirm end-to-end connectivity from the terminal:
A successful response confirms the key, URL, model ID and credits are all working correctly.
curl https://api.rutaapi.com/v1/chat/completions \
-H "Authorization: Bearer YOUR_RUTAAPI_KEY" \
-H "Content-Type: application/json" \
-d '{
"model": "MODEL_NAME",
"messages": [
{"role": "user", "content": "Hello from RutaAPI"}
]
}'Who this guide is for
This guide is for Open WebUI users who want to connect their self-hosted chat interface to an OpenAI-compatible API gateway provided by RutaAPI.
It helps if you are familiar with API keys, API URLs and the Open WebUI admin settings panel.
Who should not use this setup
- Users whose Open WebUI version does not support OpenAI-compatible provider connections.
- Users whose Open WebUI instance is configured to block external providers.
- Users who require official OpenAI-only features.
Testing before you start chatting
Before starting a chat session in Open WebUI, send a simple request from the terminal to confirm your key, URL and model IDs all work together. This rules out configuration issues before you begin.
If the first request succeeds, the Open WebUI connection should also work. If it fails, fix the terminal request first — that gives you clearer error messages than the Open WebUI UI.
How to find model IDs
Model IDs are returned by the GET /v1/models endpoint. Copy one or more of the model id values from the response.
If Open WebUI auto-detects models from /v1/models, you may not need to enter them manually. If auto-detection does not work, add the copied IDs to the Model IDs field in the connection settings.
Model availability is per-account. If a model ID is not in your /v1/models response, it is not active in your account — add more credits or contact support.
Common mistakes
- Using https://rutaapi.com as the API URL — that is the marketing site, not the API root.
- Using https://app.rutaapi.com as the API URL — that is for account management, not the API.
- Using https://api.rutaapi.com without /v1 when Open WebUI expects an OpenAI-compatible /v1 endpoint.
- Pasting https://api.rutaapi.com/v1/chat/completions as the API URL — that is an endpoint, not the root.
- Setting a RutaAPI key but keeping another provider's URL.
- Setting the URL correctly but using an API key from another platform.
- Guessing model IDs instead of using /v1/models.
- Forgetting to save or reconnect after changing settings.
- Exposing API keys in screenshots or public repositories.
Common errors
401 Unauthorized / invalid API key
The API key is missing, incorrect, or sent to the wrong URL. Verify the API key and URL both come from RutaAPI. Run /v1/models to confirm the key is valid.
403 Forbidden
The key exists but lacks permission. Check credits and model access in your RutaAPI account.
404 Model not found
The model ID is not in your account. Run GET /v1/models and copy a returned model id.
429 Too Many Requests
Rate or concurrency limit. Lower the number of concurrent requests and retry.
503 Service Unavailable
The provider route is temporarily unavailable. Try a short request, check model availability, contact support if persistent.
When RutaAPI may be a good fit
- You need an OpenAI-compatible API URL for Open WebUI
- You want dashboard-generated API keys
- You want prepaid credits
- You want to verify available models with /v1/models
- You want setup docs for Open WebUI, NextChat, Cursor, Cline, Continue.dev, Codex CLI and Claude Code
- You want usage visibility before scaling
When RutaAPI may not be the right fit
- Your Open WebUI version does not support the needed connection mode
- Your Open WebUI instance blocks external providers
- The selected model is unavailable upstream
- Your API key belongs to another provider
- You require official OpenAI-only features
Related setup and troubleshooting guides
- API Key and Base URL explained
- Unified Base URL for AI coding tools
- NextChat custom API setup guide
- Cursor custom API setup guide
- Cline OpenAI-compatible API setup
- Continue.dev OpenAI-compatible API setup
- Codex CLI invalid_api_key troubleshooting
- Claude Code 524/503 timeout troubleshooting
- Available models
- Pricing and credit packs
FAQ
What API URL should I use for RutaAPI in Open WebUI?
Use https://api.rutaapi.com/v1 — the /v1 path is the OpenAI-compatible API root. Do not use https://rutaapi.com, https://app.rutaapi.com, or any path ending in /chat/completions.
Should the URL include /v1?
Yes, if your Open WebUI version expects an OpenAI-compatible /v1 endpoint. The correct API URL is https://api.rutaapi.com/v1. Without /v1, you are pointing to the wrong endpoint and will get errors.
Can I use https://rutaapi.com as the API URL?
No. https://rutaapi.com is the marketing site, not the API root. Using it as the API URL will result in errors. Always use https://api.rutaapi.com/v1.
Can I use https://app.rutaapi.com as the API URL?
No. https://app.rutaapi.com is for account management, not the API. Using it as the API URL will result in errors. Always use https://api.rutaapi.com/v1.
Where do I get my RutaAPI API key?
Create one from the RutaAPI dashboard at https://app.rutaapi.com in the Tokens section. Keys are shown only once at creation — copy and store them securely.
How do I know which model ID to use?
Run GET /v1/models with your API key and use one of the model id values from the response. If Open WebUI auto-detects models, you may not need to enter them manually. If not, add the IDs to the Model IDs field.
What if Open WebUI does not auto-detect models?
If Open WebUI does not show models automatically, look for a Model IDs or model allowlist field in the OpenAI-compatible connection settings. Copy model IDs from /v1/models and add them there. This is a per-version feature — verify whether your installed version supports it.
Why does Open WebUI show invalid API key?
An invalid_api_key or 401 error usually means the API key does not match the URL, or it was sent to the wrong endpoint. Verify that both the API key and URL come from the same platform. Run /v1/models to confirm the key is valid.
Can a wrong URL cause 401?
Yes. If the URL belongs to a different provider than the API key, the provider rejects the key with 401. The API key and URL must come from the same platform.
What does 403 mean?
HTTP 403 means the key exists but lacks permission. Check that your account has enough prepaid credits and that the model is enabled in your account.
What does 404 model not found mean?
HTTP 404 means the model ID is not recognised at that endpoint. Run /v1/models and use one of the returned model id values as the model ID. Do not guess.
What does 429 mean?
HTTP 429 means you have hit a rate or concurrency limit. Lower the number of concurrent requests, pause parallel tasks and retry after a short pause.
What does 503 mean?
HTTP 503 means the provider route is temporarily unavailable. Try a short request, check model availability, and contact support if the issue persists.
Is RutaAPI an official Open WebUI or OpenAI service?
No. RutaAPI is an OpenAI-compatible API gateway operated by BDR FIDUCIARY LLC. It is not an official service of Open WebUI, OpenAI, Anthropic, Google or Microsoft.
Can RutaAPI guarantee Open WebUI compatibility?
No. Open WebUI provider connection settings, UI labels and support for OpenAI-compatible external providers can vary across versions and deployment configurations. RutaAPI cannot guarantee compatibility with every Open WebUI version or deployment setup.
Should I paste my API key into screenshots?
No. Never share your full API key in screenshots, forum posts, GitHub issues or any public or shared channel. If exposed, rotate it immediately from the dashboard.
What should I send to support?
Include: request time (UTC), model ID, error code, API URL, any request ID from response headers, and approximate request size. Do not share your full API key. Describe the key prefix if needed.