Reference
Reason codes
Common Valqio reason codes for runtime decisions, access checks, and settlement.
Reason codes explain why Valqio allowed, denied, or settled a runtime request.
Enforcement codes
| Code | Meaning | Retry automatically? |
|---|---|---|
ALLOWED | The action can run. | No |
SOFT_CAP | A soft usage threshold was reached. | No |
HARD_CAP | A hard usage limit blocked the action. | No |
RATE_LIMITED | A rate limit blocked the action. | Sometimes, after backoff |
INSUFFICIENT_CREDITS | The subject does not have enough credits. | No |
METER_NOT_FOUND | The request referenced an unknown meter. | No |
ENTITLEMENT_MISSING | Required access was missing. | No |
INVALID_REQUEST | The request shape was invalid. | No |
Access and parameter codes
Feature and parameter checks can also return:
PLAN_BOOLEAN_FLAG_GRANTEDPLAN_FLAG_VALUE_GRANTEDDENIED_NO_ENTITLEMENTDENIED_NO_GRANTFLAG_NOT_FOUNDCONFIG_NOT_FOUNDDEFAULT_SELECTEDVARIANT_SELECTED
Use these for product routing, support, and logs. Do not expose raw integration detail to end users.
Settlement codes
Settlement operations can return the following codes. The amount codes apply to adjustment APIs, not SDK commit or release calls.
| Code | Meaning |
|---|---|
SETTLEMENT_APPLIED | Commit or release was applied. |
SETTLEMENT_INVALID_TRANSITION | The reservation is not in a state that allows the requested command. |
SETTLEMENT_AMOUNT_REQUIRED | An adjustment omitted its target amount. |
SETTLEMENT_AMOUNT_INVALID | An adjustment target was not a positive integer. |
SETTLEMENT_NOT_FOUND | The reservation ID was not found. |
SETTLEMENT_IDEMPOTENCY_CONFLICT | The idempotency key was reused for a conflicting command. |
SETTLEMENT_BALANCE_INSUFFICIENT | Settlement could not complete because balance state no longer allows it. |
For customer responses, map reason codes to your own product language. For investigation, search Console by request ID, subject, meter, reservation ID, or idempotency key.