Endpoint page

The page for each endpoint must contain the following structure:

Use short, clear titles that fit in one line on the table of contents (ToC). Follow the standard verb pattern:

Start with a clear and concise explanation of what the endpoint does and when to use it.

List what is required to use the endpoint (e.g., authentication, permissions, required entities).

Parameters

Include all parameters, grouped by where they appear:

Document all fields that appear in the request body.

Field	Type	Required	Description	Possible Values	Default	Constraints	Example
`name`	string	Yes	Name of the account	—	—	MaxLength: 100	`"Main Account"`
`type`	string	Yes	Account type	`asset`, `liability`	—	—	`"asset"`
`assetId`	string	Yes	Associated asset ID	—	—	UUID	`"01fbc1..."`

Describe what users receive when the request is successful. Include status codes like 200, 201, or 204.

All errors must follow Lerian’s standard error format. Include every possible error the endpoint can return.