Logs - BabySea Docs

Logs show requests made with BabySea API keys. Use them to debug authentication, scope failures, rate limits, provider errors, and usage patterns.

What is logged

Each row joins request metadata with key metadata.

Field	Description
API key name	Name assigned when the key was created.
Key prefix	First 9 characters of the key, used for identification.
Method	HTTP method.
Endpoint	API path.
Query params	Sanitized query string values.
Status code	HTTP response status.
Error code	`BSE` code when the request failed inside BabySea.
Replay	Whether the request returned an idempotency replay.
IP hash	SHA-256 hash of the client IP. Raw IPs are not shown.
User agent	Client user agent.
Timestamp	Request timestamp.
Key status	Whether the key is active, expired, or rotated.

Logs do not store request bodies or raw API keys.

The search box filters visible rows by:

Select rows, then use the table action menu to:

The page displays 500 rows per page. For wide tables, use the fullscreen view from the top-right action button.

Filter by BSE1002 or HTTP 401. Check whether the key is expired, revoked, from the wrong region, or copied incorrectly.

Filter by BSE1003 or HTTP 403. Compare the endpoint with the key scopes in API keys.

Filter by BSE1007. Add the calling server IP to the key allowlist or remove the allowlist for dynamic client environments.

Filter by BSE1005 or HTTP 429. Account-level rate limits are shared by all keys in the account.

Filter by BSE4. Inference provider errors include timeouts, unavailable providers, upload failures, and all-provider failure states.

API request logs are pruned by plan:

Records expire according to the retention window for the account plan.