Pre-check states before every invoice
Use supported-states to prevent unsupported workflows before they create operational noise.
Finance admins, Project operations teams, API implementers4 min readUpdated 2/9/2026
Pre-check states before every invoice
This is the fastest way to reduce invalid requests in your first week.
Endpoint: GET /api/v1/supported-states
If you accept invoices across many states, you need this check before calculation logic runs.
Expected response
states: array of two-letter state codescount: number of active supported states
Real-world impact
Without this check
- failed calls
- confusing user-facing errors
- missed opportunities to route work correctly
With this check
- immediate validation
- faster exception handling
- cleaner closeout data quality
Example use in a pilot
- Load the supported list at startup.
- Validate each invoice state against the list.
- If unsupported, assign to manual review and note the reason.
- If supported, continue to
/api/v1/calculate-deadline.
Ready for a live walkthrough?
Use the guided API sandbox with realistic contractor/owner scenarios and test preconfigured payloads in under 5 minutes.