ogify
Docs

Authentication

Every production request to Ogify should include an API key. Keep it secret, rotate it when needed, and never ship it in public client code.

Obtain an API key

Sign in to your dashboard, open the API keys panel, and copy your active key.

Keys are shown once after creation. Store them in your server environment variables.

Pass the key

Send the key with the `x-api-key` header.

curl -X POST https://api.ogify.dev/render/template \
  -H "x-api-key: $OGIFY_KEY" \
  -H "Content-Type: application/json" \
  -d '{"template":"blog","title":"Launch notes"}'

Query-string API keys are not recommended. Use headers unless your integration cannot send custom headers.

Rotation and security

  • Rotate keys from the dashboard if a key is exposed.
  • Use one key per environment so staging and production can be revoked separately.
  • Never place API keys in frontend JavaScript, mobile apps, or public repositories.