Guides
Data API Overview
Call third-party endpoints through one shared prefix, with consistent authentication and request handling.
The Data API is a catalog of third-party APIs behind one Felo key. It is separate from Felo's own /v2 APIs and from the Model API.
Shared prefix
https://openapi.felo.ai/v1/betaThe reference shows each endpoint as a full path beginning with /v1/beta. Use that path as-is on the host; do not prepend the shared prefix again. For example, the Tavily search endpoint is:
POST https://openapi.felo.ai/v1/beta/tavily/searchFind an endpoint
- Browse the API directory by supplier.
- Open the Data API reference for the full endpoint list, parameters, and response schemas.
- Use the reference's tags to move between suppliers.
Each supplier keeps its own request shape. The shared layer standardizes authentication and routing, not the payload. Read the endpoint schema before sending a request.
Authentication
Use either header:
Authorization: Bearer $FELO_API_KEYor:
X-API-Key: $FELO_API_KEYSend Content-Type: application/json for JSON bodies.
Example request
curl https://openapi.felo.ai/v1/beta/tavily/search \
-H "Authorization: Bearer $FELO_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"query": "What is Felo AI?",
"max_results": 3
}'The response shape comes from the supplier. Fields such as results, pagination cursors, and metadata are not normalized across providers.
Conventions
| Topic | What to expect |
|---|---|
| Payload | Supplier-specific JSON; follow the endpoint schema |
| Pagination | Field names and cursor styles vary by endpoint |
| Errors | JSON with status, code, message, and request_id; provider details may appear in the message |
| Rate limits | Endpoint and supplier specific; expect 429 under load |
| Billing | Per call, from the same service credit balance as the Model API |
Error handling
An authentication failure returns the same envelope as the rest of the platform:
{
"status": 401,
"code": "UNAUTHORIZED",
"message": "Invalid API Key",
"request_id": "..."
}For a provider-level failure, read the HTTP status and the message. Log the method, full path, request body shape, and request_id. Do not log the full API key.
Retries
Retry 429 and 5xx responses with backoff. Do not retry 400 or 401 unchanged. Some provider operations are not safe to repeat; check the endpoint before retrying a write.
When to use a Felo API instead
Use the Data API when you need a specific third-party data source. Use a Felo API when you want Felo's own workflow:
- Search-grounded answers with citations: Chat API
- Slide generation: PPT Task API
- Landing pages: Landing Page Task API
- Knowledge bases and retrieval: LiveDoc API
- Agent conversations with streaming: SuperAgent API