OPERATIONS
Commercial exceptions
Most bookings should pass quietly. Consequential, evidence-backed findings are returned in the same API response.
Understanding findings
A result with data.status = EXCEPTION includes one or more data.exceptions, each with a stable ID, type, reason, audience, severity, governing agreement and supporting evidence references.
The implemented named-account restriction identifies a contract rate matching the lane and equipment but excluding the supplied named account. Contract-rate conflict detection is also present. The set is not a complete commercial audit policy.
Do not infer financial liability
- financialExposureMinor is null when liability cannot be established. Null is not $0.
- matchedRateIds do not establish an all-in buy rate, payable charge or guaranteed saving.
- INSUFFICIENT_EVIDENCE means evidence cannot support a final commercial decision; it does not automatically imply a breach.
- Return the exception to Regional Operations through your own forwarding-system integration. Foryn does not currently push outbound customer webhooks.
Response handling
Keep a record of data.status, source booking reference, revision, exception ID and evidence identifiers. Never require an optional resolution as a condition for routine intake.
Use the fictional response file /developers/v1/examples/response-exception.json as a structural reference, not proof that its exact IDs exist in your environment.