Create an expense report
Planned API — Reference OnlyProposed creation operation for expense-reports. Educational design only; no route, database operation or external access is implemented.
/v1/expense-reportsProposed behavior
This endpoint specification is an illustrative design, not a published operational contract. It cannot be called from this site and does not exist as a documentation backend route.
Proposed authentication and permissions
Proposed bearer API key or OAuth access token. Authentication is not implemented.
Proposed expense-reports:write scope. No permissions are currently issued or enforced by a public API.
Illustrative request parameters
No query parameters are illustrated for this operation.
| Name | Type | Description |
|---|---|---|
| titlerequired | string | Proposed report title. |
| expense_idsrequired | string[] | Fictional expense identifiers; no records are referenced or modified. |
Static example request
Every example uses a reserved .example hostname and YOUR_API_KEY. Language tabs and Copy only change or copy text; they never execute it.
# Reference only. Placeholder host and credential; do not run against production.
curl -X POST "https://api.remizen.example/v1/expense-reports" \
-H "Authorization: Bearer YOUR_API_KEY" \
-H "Content-Type: application/json" \
--data '{"title":"Example expense report","expense_ids":["exp_example"]}'Static example response
Sample data only. No request was sent and no records were read or written.
{
"id": "rpt_example",
"title": "Example expense report",
"expense_ids": [
"exp_example"
],
"status": "draft"
}Proposed status codes
| Code | Illustrative meaning |
|---|---|
| 201 | Illustrative successful response; no request has been performed. |
| 400 | Proposed invalid-input response; format subject to change. |
| 401 | Proposed authentication error; token validation is not implemented. |
| 403 | Proposed permission error; scope enforcement is not implemented. |
| 429 | Potential rate-limit response; no rate policy is established. |