Skip to main content
Klipeo
Klipeo Docs
API

API Overview

The Klipeo HTTP API. Bearer-token auth, JSON, rate limits, and an OpenAPI spec.

Klipeo has a REST API for working with your projects, uploads, and Vibe from your own code. It's plain HTTP and JSON, and it authenticates with the API keys you create in settings.

Base URL and version

Everything lives under the v1 path:

https://klipeo.com/api/v1

Authentication

Send your key as a bearer token on every request:

curl https://klipeo.com/api/v1/me \
  -H "Authorization: Bearer klipeo_sk_your_key_here"

The key's scopes decide what it can do. A read-only key is rejected on any request that writes (uploads, creates, and all of /api/v1/generate/*), with a 403. A key can also carry an expiry — once past it, requests come back 401 Invalid or revoked API key.

Rate limits

Calls are counted per account, per day, resetting at midnight UTC. All of your keys share the same daily quota, so making more keys doesn't buy more calls.

AccountCalls per day
Standard1,000
Upgraded10,000
AdminUnlimited

Every response carries the current state in headers, so you don't have to guess:

X-RateLimit-Limit: 1000
X-RateLimit-Remaining: 994
X-RateLimit-Reset: 2026-05-29T00:00:00.000Z

OpenAPI spec

There's a machine-readable spec you can import into Postman, an SDK generator, or your editor:

GET /api/v1/openapi.json

It needs no auth. The full list of endpoints is on the Endpoints page.

Keep your keys safe

Treat a key like a password. Don't commit it or put it in client-side code. If one leaks, revoke it and issue a new one.

On this page