The API provides three views with different evidence and identifier requirements. A submission acknowledgement establishes recorded acceptance only. An upstream fill report does not establish verified destination delivery. The on-chain view sets top-level filled only after matching every output of the verified Open. Settlement requires a separate origin event. For openFor orders, the Infinity Hub status endpoint remains at CREATED. Use upstream status with its chain projection or the on-chain fill view to track their progress.

Missing and stale data

upstreamStale identifies an upstream view without current confirmation. upstreamUnavailable identifies a chain-only response when the upstream record is unavailable. In that response, state and upstream history can be absent. Observer watermarks describe the coverage behind chain views. A stale watermark cannot support a fresh claim that no fill exists. Poll at a bounded interval consistent with the endpoint’s cache and rate limits.

Failure and completion

An upstream failed state can later advance after a solver fills the order. finalized and refunded are terminal upstream states, but they remain reports from that interface. Use confirmed chain evidence when the application requires contract-level completion. See order construction and lifecycle.