sipi.bot API Error Codes
Every error the sipi.bot API returns, what it means, and how to fix it. Error names and HTTP statuses match the live API exactly.
invalid_api_key — HTTP 401
The Authorization header was supplied but couldn't be resolved to a valid API key. sipi.bot never silently downgrades an invalid paid key to anonymous behavior — it rejects the request.
api_key_required — HTTP 401
The request hit a route that requires authentication, and no valid Authorization header was sent.
forbidden — HTTP 403
The request was authenticated but the caller lacks permission for the operation.
not_found — HTTP 404
The requested route or resource doesn't exist.
method_not_allowed — HTTP 405
The route exists but doesn't accept the HTTP method you used.
body_too_large — HTTP 413
The request body exceeded the server's size limit.
rate_limited — HTTP 429
Too many requests in the rate-limit window. The response includes retry_after — honor it.
transaction_error — HTTP 400
The transaction payload failed validation. The API returns a specific error name — amount_required, invalid_amount, or invalid_<field> — telling you exactly which field is wrong.
rule_error — HTTP 400
The rule payload failed validation. The API names the exact problem: invalid_rule_type, invalid_rule_action, invalid_rule_params, invalid_rule_priority, or invalid_rule_label.
internal_error — HTTP 500
Something failed inside the service. 500s are rare; when they happen, they're the API saying 'try again, or check the status page'.
Stop the next $12,400 night.
One API call (or MCP tool) in front of every agent transaction — APPROVED, BLOCKED, or FLAGGED, deterministic, ~5 ms, fully logged.
See plans — from $99/mo Try a live check