Appearance
Authentication
Genium APIs use a user API key in the Authorization header:
bash
export USER_API_KEY="..."
curl https://auth.genium.one/api/social/accounts \
-H "Authorization: Bearer $USER_API_KEY"Keep the key server-side. Do not put it in browser JavaScript, local storage, public documentation examples, or source control.
Rotate a key
bash
curl -X POST https://auth.genium.one/api/user/api-key/rotate \
-H "Authorization: Bearer $USER_API_KEY"The new key is returned once. Update the calling service immediately and revoke the old key according to your deployment process.
Connect a provider
Create a short-lived connect ticket with the authenticated user key:
bash
curl -X POST https://auth.genium.one/api/social/connect-ticket \
-H "Authorization: Bearer $USER_API_KEY" \
-H "Content-Type: application/json" \
-d '{"provider":"sheets"}'Open the returned connect_url in a browser. Tickets are one-time use and expire quickly.