Update Allowance — Proposed Guide
Planned API — Reference OnlyUpdate Allowance: An allowance update would change permitted future-facing attributes with version control. Reducing an allocation below already consumed…
Overview
An allowance update would change permitted future-facing attributes with version control. Reducing an allocation below already consumed amounts needs an explicit exception policy.
Key concepts
Distinguish the assigned amount from recorded consumption. Preserve the effective date of the change.
Implementation considerations
Do not rewrite historical transactions to make a new balance appear valid. Closed periods should remain protected from ordinary edits.
Proposed API behavior
PATCH /v1/allowances/{allowance_id} is an illustrative design for this topic. Path and field names may change before implementation. Access would require an authorized organization context and operation-specific permission; no public API or authorization grant is available here.
| Name | Type | Description |
|---|---|---|
| allowance_idrequired | string | Stable fictional allowance reference; not a secret and not evidence that a resource exists. |
| Name | Type | Description |
|---|---|---|
| amount_minor | integer | Monetary amount in the documented currency minor unit; 12550 represents USD 125.50, not USD 12,550. |
| effective_on | string (date) | Synthetic calendar date in YYYY-MM-DD form; period inclusivity must be defined by the future contract. |
| version | integer | Illustrative resource revision for detecting stale updates; no live concurrency contract is published. |
Static example requests
# Proposed request text only; this reserved host is not a live API.
curl -X PATCH 'https://api.remizen.example/v1/allowances/allowance_example_123' \
-H 'Authorization: Bearer YOUR_API_KEY' \
-H 'Content-Type: application/json' \
--data '{
"amount_minor": 12550,
"effective_on": "2026-01-15",
"version": 1
}'Fictional response example
Fictional documentation data only. No request was sent, record created, review performed, payment initiated or provider connection activated.
{
"data": {
"allowance_id": "allowance_example_123",
"amount_minor": 12550,
"effective_on": "2026-01-15",
"version": 1,
"id": "allowances_example_123",
"organization_id": "org_example_123"
},
"meta": {
"request_id": "req_example_123",
"reference_only": true
}
}Illustrative error case
Review this failure case in context: Do not rewrite historical transactions to make a new balance appear valid. Closed periods should remain protected from ordinary edits.
Synthetic diagnostic example. Human-readable messages must not be used as stable programmatic contracts.
{
"error": {
"code": "validation_error",
"message": "The proposed update allowance operation requires review of its input or authorization.",
"request_id": "req_example_123"
}
}Proposed data types
| Name | Type | Description |
|---|---|---|
| allowance_id | string | Stable fictional allowance reference; not a secret and not evidence that a resource exists. |
| amount_minor | integer | Monetary amount in the documented currency minor unit; 12550 represents USD 125.50, not USD 12,550. |
| effective_on | string (date) | Synthetic calendar date in YYYY-MM-DD form; period inclusivity must be defined by the future contract. |
| version | integer | Illustrative resource revision for detecting stale updates; no live concurrency contract is published. |