Developer reference
API reference
Start with authentication, scopes and request conventions for Helm’s registered HTTP API.
Helm’s API is rooted at /api/v1. The financial surface uses /api/v1/v2. Use the canonical application origin, https://helm.neuroom.io, for the public product.
Make your first read
Start with the read-only quickstart. It creates a minimum-scope user token and requests the caller’s accounts. Do not use a privileged database key as an integration credential.
Reference map
| Need | Read |
|---|---|
| Identify the caller | Authentication and API tokens. |
| Choose permissions | Scopes. |
| Parse responses | Conventions, errors and pagination. |
| Recover a money command | Idempotency. |
| Find a method and path | Registered endpoint catalog. |
| Build a client | Client integration and rate limits. |
Contract boundaries
Resource IDs must belong to the authenticated user. The registered operation list states methods and scopes; request validation and financial constraints still apply. Some first-party read branches are not part of the API-token registry.
This API is coupled to the deployed Helm version. A machine-readable manifest does not establish a hosted MCP transport or every future integration. Read current boundaries before depending on a planned capability.