Build on AI Ad Clone with one API key.
A secure REST API for AI Ad Clone. Send one header, get JSON back. Request a key, make your first call in minutes, and plug it into any backend.
curl {{BASE}}/status \ -H "X-API-Key: $API_KEY"
import os, requests r = requests.get( "{{BASE}}/status", headers={"X-API-Key": os.environ["API_KEY"]}, timeout=10, ) print(r.json())
const res = await fetch("{{BASE}}/status", { headers: { "X-API-Key": process.env.API_KEY }, }); console.log(await res.json());
{
"message": "AI Ad Clone API is running",
"authenticated": true
}
Everything you need to integrate, nothing you don't
A small, predictable API with secure defaults, clear errors and docs that are generated straight from the code.
Simple key auth
Send your key in X-API-Key or as a Bearer token. Keys are compared in constant time, so timing reveals nothing.
HTTPS everywhere
Every request is encrypted with TLS, with HSTS on. Your key never travels in plain text.
Docs from the source
An OpenAPI spec generated from the code, plus Swagger UI and ReDoc. The docs can't drift from the API.
Traceable requests
Every response carries an x-request-id. Quote it to support and we can find your exact call.
Rotation without downtime
Old and new keys work side by side during a rotation, so you can switch over without a single failed request.
Predictable JSON
JSON in, JSON out. Every error has a documented status code and body, so it's easy to handle in any language.
From zero to first call in three steps
No SDK to install. If your stack can make an HTTPS request, it can use this API.
Request a key
Tell us who you are and what you're building. Once approved, your key is sent to you privately.
Request access →Store it safely
Put the key in an environment variable or secret manager on your server, never in front-end code.
# .env on your server API_KEY=your-key-here
Make your first call
Call /status with your key. A 200 means you're connected.
curl {{BASE}}/status \ -H "X-API-Key: $API_KEY"
Clear errors, so you're never guessing
Authentication failures return a machine-readable code and a human-readable message, and every response carries a request ID for support.
- 401 means the key is missing or wrong. The message tells you which.
- x-request-id on every response, success or failure.
- Try it live from the docs: paste your key and send real requests from the browser.
curl -i {{BASE}}/status
{
"error": "invalid_api_key",
"message": "Missing API key. Send it as 'X-API-Key: <key>'
or 'Authorization: Bearer <key>'."
}
Questions, answered
How do I get an API key?
Request access by emailing the API owner with your name, project and expected usage. Once approved, you'll receive a key privately. The full steps are in the documentation.
How do I send the key?
Add X-API-Key: <your key> to every request, or Authorization: Bearer <your key>. Both work the same way.
Can I call the API from a browser or mobile app?
No. Anyone can read a key that ships in front-end or app code. Call the API from your own server and have your app talk to your server.
What if my key leaks or I lose it?
Contact us straight away. We'll revoke the old key and issue a new one. During a planned rotation, old and new keys work side by side, so you have no downtime.
Where is the full endpoint reference?
In the documentation, with live Try it buttons. The interactive Swagger UI, ReDoc and the raw OpenAPI spec are also available.
Ready to build?
Request your API key today and make your first call in minutes.