Authentication

Every request to the Repurai API must be authenticated using an API key. You can generate and manage your keys in the API Keys dashboard.

API Keys

API keys follow the format rep_<64-hex-chars>. Each key is shown once at creation time — copy it immediately and store it securely.

Pass the key in the Authorization header using the Bearer scheme:

curl https://repurai.com/api/v1/feeds \
  -H "Authorization: Bearer rep_your_api_key"

Never include your API key in client-side code, public repositories, or logs. Use server-side environment variables.

Store in environment variables — never hard-code keys in source files.
Rotate regularly — revoke old keys from the dashboard and issue new ones.
One key per integration — assign a descriptive name to each key so you know exactly which service uses it.
One-time visibility — Repurai only displays the raw key once upon creation. If you lose it, revoke it and create a new one.

Store in environment variables — never hard-code keys in source files.

Rotate regularly — revoke old keys from the dashboard and issue new ones.

One key per integration — assign a descriptive name to each key so you know exactly which service uses it.

One-time visibility — Repurai only displays the raw key once upon creation. If you lose it, revoke it and create a new one.