Marketfront API
Order Lifecycle
Understand the complete order flow from validation through fulfillment.
Order Flow
Every order goes through two API steps: validation and placement.
Order State & Status
Orders use two fields: state (lifecycle position) and status (granular progress).
State
Status
Within the open state, status tracks progress:
For complete details on state values, status values, and error codes, see the API Reference.
Idempotency
POST /v1/marketplace/orders/place requires an Idempotency-Key header. Calls without it are rejected with a 400 ProblemDetail (errorCode: MISSING_IDEMPOTENCY_KEY).
- Generate a fresh UUID v4 per distinct order and include it on every retry of that order.
- A replay with the same key returns the original response (24h TTL) — safe to retry on network errors and 5xx without risking a duplicate charge.
- Do not reuse a key with a different payload. Today the cached response is returned regardless of body; a future release will reject same-key/different-body with
422. Keep keys 1:1 with payloads now to avoid surprises.
validate is naturally idempotent (read-only pricing) and does not use the header.
Related
- Validate Order — Check availability and pricing
- Place Order — Submit order for fulfillment
- Payments — Payment options and Card-on-File setup
- Webhooks — Signature verification and retry policy for order status webhooks