Direct HTTP access to all APIs from any language or HTTP client. No SDK required.
https://api.apiclearinghouse.comAll endpoints require HTTPS. HTTP redirects to HTTPS automatically.
All proxy calls require an API key (chk_live_...). Get your key from the dashboard.
Option 1 — X-Api-Key header (recommended)
curl -s "https://api.apiclearinghouse.com/v1/call/weather/current?lat=48.85&lon=2.35" \
-H "X-Api-Key: chk_live_YOUR_KEY"Option 2 — Bearer token
curl -s "https://api.apiclearinghouse.com/v1/call/weather/current?lat=48.85&lon=2.35" \
-H "Authorization: Bearer chk_live_YOUR_KEY"Both auth methods accept clearinghouse API keys directly. Bearer tokens are also accepted for session JWTs from POST /v1/auth/login.
All API proxy requests go through /v1/call/{api-slug}/{endpoint}. Query parameters are forwarded to the upstream API.
| Example | What it calls |
|---|---|
| /v1/call/weather/current?lat=48.85&lon=2.35 | Current weather in Paris |
| /v1/call/crypto-prices/price?symbol=BTC | Live Bitcoin price |
| /v1/call/geocoding/search?q=Berlin | Geocode "Berlin" |
| /v1/call/public-holidays/holidays/2025/DE | German public holidays 2025 |
The catalog endpoint is public — no auth required. Returns all active APIs with endpoints, parameters, and health scores.
curl -s "https://api.apiclearinghouse.com/v1/catalog"Or browse the full API catalog in the UI.
A full OpenAPI 3.1 spec is available for SDK generation, Postman import, or any OpenAPI-compatible toolchain.
View OpenAPI spec →Import into Postman: Import → Link → paste the URL above
All errors return a consistent JSON envelope with a machine-readable code and an agent-friendly hint:
{
"status": "error",
"error": {
"code": "RATE_LIMIT_EXCEEDED",
"message": "Rate limit exceeded",
"hint": "Upgrade your plan for higher limits.",
"docs": "https://apiclearinghouse.com/docs"
}
}