# 18 — HTTP REST API GoClaw exposes a comprehensive HTTP REST API alongside the WebSocket RPC protocol. All endpoints are served from the same gateway server and share authentication, rate limiting, and i18n infrastructure. Interactive documentation is available at `/docs` (Swagger UI) and the raw OpenAPI 3.0 spec at `/v1/openapi.json`. --- ## 1. Authentication All HTTP endpoints (except `/health`) require authentication via Bearer token in the `Authorization` header: ``` Authorization: Bearer ``` Two token types are accepted: | Type | Format | Scope | |------|--------|-------| | Gateway token | Configured in `config.json` | Full admin access | | API key | `goclaw_` + 32 hex chars | Scoped by key permissions | API keys are hashed with SHA-256 before lookup — the raw key is never stored. See [20 — API Keys & Auth](20-api-keys-auth.md) for details. > Some endpoints accept the token as a query parameter `?token=` for use in `` and `