REST API
Authentication
Authenticate REST API requests with revocable MakeInfluencer API keys and keep production credentials safe.
Create a key
Create a named, revocable key in Developer API → Keys. The secret is shown once. Store it in your deployment platform's secret manager, not in source control or browser code.
Keys identify one MakeInfluencer account
Requests use that account's model access and shared credit balance. Create separate keys for local development, staging, and production so each can be revoked independently.
Send the key
Send the key as a Bearer token on every REST request.
Authorization header
curl https://www.makeinfluencer.ai/api/v1/account \
--header "Authorization: Bearer $MAKEINFLUENCER_API_KEY"A missing, invalid, or revoked key returns401 unauthorized. API keys must never be placed in query strings.
Key lifecycle
CreateChoose a name that identifies the environment or service.
UseSend the secret only from trusted server-side code.
ObserveReview last-used timestamps in the Developer API workspace.
RotateCreate the replacement, deploy it, then revoke the old key.
RevokeRevocation takes effect for subsequent authenticated requests.
Security checklist
- Keep keys in server-side environment variables or a managed secret store.
- Never expose a key in frontend JavaScript, logs, screenshots, or support tickets.
- Use one key per environment and revoke keys that are no longer active.
- Treat a copied or committed key as compromised and rotate it immediately.