Authentication

Every request to /v1 carries your API key in the Authorization header:

Authorization: Bearer crier_live_…

Creating and revoking keys

• Create them in the dashboard, under API keys. The full secret is shown once; afterwards you only see its prefix.
• Create one per environment or service (production, staging…) so you can revoke them separately.
• Revoking a key invalidates it at once.
• For safety, keys cannot create or revoke other keys: that only happens in the dashboard.

Good practice

• Use it only from your server. Never in a mobile app or the browser.
• Keep it in a secrets manager or an environment variable, not in your code.
• If it leaks, revoke it and create another.

Workspace

Each key belongs to a workspace: everything it creates (profiles, accounts, posts) belongs to that workspace. Check which workspace you are calling as:

curl "https://api.usecrier.com/v1/me" \
  -H "Authorization: Bearer $CRIER_API_KEY"

const res = await fetch('https://api.usecrier.com/v1/me', {
  headers: {
    Authorization: `Bearer ${process.env.CRIER_API_KEY}`,
  },
});
const { data } = await res.json();

import os, requests

res = requests.get(
    "https://api.usecrier.com/v1/me",
    headers={"Authorization": f"Bearer {os.environ['CRIER_API_KEY']}"},
)
data = res.json()["data"]