> ## Documentation Index
> Fetch the complete documentation index at: https://spiceflow-docs.spicenet.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Managed Orders API

> Venue-specific order readiness, signed amendments and revision history

The managed `/orders` API is distinct from generic [conditional intents](https://spiceflow-docs.spicenet.io/api-reference/endpoint/conditional-intents.md). Use the matching SDK controller and supported venue configuration. Do not use the readiness of one service as the readiness of the other.

## Endpoints

| Method | Endpoint | Purpose |
| - | - | - |
| `GET` | `/orders/status` | Read `placementReady`, `recoveryReady`, active capacity and available slots. |
| `POST` | `/orders` | Register a signed managed order. |
| `GET` | `/orders?user=:address&after=:orderId` | List an owner's managed orders. |
| `GET` | `/orders/:id` | Read an exact signed revision. |
| `GET` | `/orders/:id/current` | Resolve a stable order ID to its current revision. |
| `GET` | `/orders/:id/revisions` | Read the order's revision history. |
| `POST` | `/orders/:id/amend` | Submit `{ replacement }` with a newly signed replacement order. |
| `POST` | `/orders/:id/cancel` | Submit `{ signature }` for cancellation of the signed revision. |

`/orders/status` returns endpoint-specific readiness rather than a fill guarantee. A `false` placement flag can coexist with working reads and recovery. Preserve history and cancellation access when new placements are unavailable.

## Signed revisions

Returned orders expose `orderId`, `revisionId` and `revision`. Keep stable order identity separate from the signature and exact revision being amended or cancelled. Editing amount, limit, timing or other signed terms requires a fresh accepted preview and signature.

A replacement is a new immutable signed revision. The API arbitrates replacement, cancellation and execution ownership. An execution already claimed by the worker can prevent an amendment or cancellation; handle `409` by reading the current order rather than claiming success or submitting a duplicate.

Registration returns `201` when accepted. Acceptance does not mean the order filled. Read its status, transaction evidence and settlement result through the matching order controller. Execution belongs to the managed-order worker, so manual action-step execution is rejected.

For a new trigger-based integration, start with the [conditional intent guide](https://spiceflow-docs.spicenet.io/guides/conditional-intents.md) and its configured evaluator instead of constructing a venue-specific managed-order payload by hand.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.