Every request carries your API key in the Authorization header:
curl https://api.bluwing.si/v1/chat/completions \
-H "Authorization: Bearer $BLUWING_API_KEY" \
-H "Content-Type: application/json" \
-d '{ "model": "bluwing", "messages": [{ "role": "user", "content": "Ping" }] }'Your key
Each account has one key. Find it on the console's API key page. Showing it asks you to confirm your password if you signed in more than 15 minutes ago, and the page records when it was last shown.
Keys look like rk_live_ or rk_test_, then an 8-character id, then a 40-character secret. The prefix up to the id is safe to log; the rest is not.
A key can do everything an account can through the API: build and delete toolsets, and send requests. It can't change your plan or buy credits; those happen in the console.
Requests with a body
Send JSON with Content-Type: application/json. Anything else answers 415 UNSUPPORTED_MEDIA_TYPE. Bodies are limited to 1 MiB (413 PAYLOAD_TOO_LARGE).
When it goes wrong
| Status | Code | Cause |
|---|---|---|
| 401 | INVALID_API_KEY | Missing, malformed, wrong or revoked key. |
| 403 | FORBIDDEN | The key exists but isn't allowed to do this. |
Keeping it safe
- Call from your server. A key in a web page or a mobile app can be read by anyone who has the app.
- Load it from the environment or a secret manager. Don't commit it.
- Don't log full request headers.
- If it leaks, write to [email protected] from your account's email address. We revoke it and issue a new one the same day. Self-serve rotation is coming.
Every response has an X-Request-Id header. Include it when you contact support about a request.