Authentication
Pass your API key as a Bearer token on every request. Keys are created once in the dashboard. and shown only at creation time.
Header
Send the key in the Authorization header. Do not put the key in query strings or request bodies.
Authorization: Bearer sk_live_...Example
curl -s 'https://trysocify.com/api/v1/instagram/user?username=natgeo' \ -H "Authorization: Bearer $SOCIFY_KEY"
Error responses
Auth failures always return HTTP 401 with the same short body. Socify never reveals whether a key is missing, malformed, revoked, or unknown : treat every unauthorized as “fix the key and retry.”
| Cause | When it happens | What to do |
|---|---|---|
| Missing header | No Authorization header, or it is empty. | Add Authorization: Bearer …. |
| Wrong scheme | Header present but not Bearer (e.g. Basic, raw key, or Token). | Use the Bearer scheme exactly. |
| Invalid key | Typo, truncated secret, extra whitespace, or a key that never existed. | Copy the key again from creation time, or create a new one. |
| Revoked key | Key was revoked or deleted in the dashboard. | Create a replacement key and update your env / secrets store. |
| Wrong environment var | Client sends a placeholder like $SOCIFY_KEY literally, or an empty string. | Export the real secret before calling the API. |
Response body
HTTP/1.1 401 Unauthorized Content-Type: application/json { "error": "unauthorized" }
Related (not auth): if the key is valid but the account has no remaining credits, you get 402 with insufficient credits : see Credits and Errors.