Authentication

repsapi.pl uses bearer API keys. Create an account to generate one, then send it in the Authorization header on every request.

Your API key

Keys look like rk_live_…. Grab one from your project menu after you create an account. Treat it like a password - never ship it to the browser.

Making an authenticated request

terminal

curl "https://repsapi.pl/v1/tracking?num=YT2530998211074512" \
  -H "Authorization: Bearer YOUR_API_KEY"

API keys are accepted only in the Authorization header. They are never accepted in the URL, where browser history, proxy logs and analytics could expose them.

From code

Any HTTP client works. The official SDKs (npm install repsapi, pip install repsapi) send the header for you.

index.ts

const res = await fetch("https://repsapi.pl/v1/usage", {
  headers: { Authorization: `Bearer ${process.env.REPSAPI_KEY}` },
});
console.log(await res.json()); // plan, today's usage, remaining quota

Good to know

Keys are scoped to a single project. Each project can be limited to some endpoints, a daily cap and an IP whitelist.
Rotate a key anytime. The previous key has a 24-hour migration window.
Server-side only. For browser apps, proxy requests through your backend.