Authentication

Every Serplify API request is authenticated with an API key sent as a Bearer token in the Authorization header.

Authorization: Bearer live_your_key_here

Getting a key

1. Sign in at app.serplify.io.
2. Go to API keys.
3. Create key — pick a label and live or test prefix.
4. Copy the key immediately. The plaintext is shown once and never again.

Keys are scoped to your account and share your account’s single prepaid balance. You can create multiple keys (e.g. per environment or per service) and revoke or reactivate any of them at any time.

Missing or invalid keys

On the native /v1 API, an authentication failure returns a real HTTP status:

HTTP 401

{ "error": { "code": "unauthorized", "message": "Missing or invalid API key." } }

Situation	HTTP	error.code
No Authorization header	401	unauthorized
Unknown / revoked key	401	unauthorized
Balance too low for the request	402	insufficient_balance

DataForSEO drop-in

The legacy /v3 API mirrors DataForSEO: it always returns HTTP 200 and carries the real status in the body (40101 auth error, 40402 insufficient funds). See the migration guide.

Keeping keys safe

• Never embed a live_ key in client-side code or a public repo.
• Use test_ keys in development.
• Revoke a key the moment it may have leaked — revocation is instant.