Create order

POST /v1/order Register acceptance of an open-flow winner, after the user sent the disclosed executionTx themselves (paying the gas). One order per quote. Only for an open-flow winner (the SDK’s lane is open-flow): every OIF-lane quote is refused EIN0007 at the re-approval step (known issue).

Item	Value
Route key	`infinityOrderCreate`
Credential	API key or project id
`X-Infinity-Subject`	required: the subject the quote was made for (Authentication — your users)

Request

Request body

OrderCreateRequest:

Field	Type	Required	Rules	Meaning
`quoteRequestId`	string	yes	≤ 128	from the quote
`quoteId`	string	yes	≤ 128	from the quote
`artifactHash`	string	yes	≤ 256	echo of `disclosure.signableHash`; the hub recomputes its own and compares (a cross-check, never authority)
`signature`	string	together	≤ 512	`personal_sign` over `signIntent`
`signer`	string	together	≤ 128	must equal the quote’s `sourceAccount` (0x addresses compare case-insensitively)
`scheme`	string	together	`eip191` (for `personal_sign`), `eip712` or `ed25519`	the signature scheme

Response

data (OrderCreateAck):

Field	Type	Meaning
`orderId`	string	64 hex, `hex(sha256("infinity:v1:order:" + quoteId))`
`quoteId`	string	echoed
`createdAt`	timestamp	the first acceptance
`status`	string	always `CREATED`; everything after is asynchronous — read `GET /status/{orderId}`

Behavior

signature, signer and scheme go together — all three or none. Any one present makes all three required; a partial set is EIN0010. A quote requested without sourceAccount therefore cannot be signed.
None is admitted only when the deployment enables unsigned registrations (infinity.flags.orderSignatureOptional); otherwise EIN0010.
The hub re-approves the winner (product enabled, class admissibility, fingerprint) before the artifactHash and signature checks; a failure is EIN0007. POST /order registers create-flow winners only. Every OIF-lane quote answers EIN0007 here; complete it through POST /order/openfor. Decide with the SDK’s detectLane(q) (known issue).
A proxy-lane executionTx is not registered here (EIN0007) — it completes through POST /order/openfor, unsigned.
Register before expiresAt, and never re-quote after the transaction. The user’s transaction is already sent when this call is made, and a first registration at or after expiresAt (about 30 s after issue) is EIN0005. A refused registration doesn’t undo the transaction: it completes on chain anyway, unregistered, and a new quote would mean a second transaction. The same holds for EIN0006, EIN0007 and EIN0010 below; proxy-lane registrations follow the same rule (known issue).
Rate limit. Every request whose body validates, a duplicate included, is charged to your organization’s order bucket (Limits) before the quote is read; a shed is EIN0080.
Idempotent: a repeat for a quote that already has an order — including one created through POST /order/openfor — gets that order’s ack (same orderId and quoteId, and the first createdAt). It is answered right after the quote’s own checks (known, yours, quoted) and before the expiry, configuration, re-approval, artifactHash and signature checks, so it holds after expiresAt, after a configuration change (no EPOCH_SUPERSEDED is recorded), and whatever artifactHash or signature fields the repeat carries. A lost ack is recovered by re-posting.

Errors

Code	When
`EIN0001`	form, `body` (well-formed JSON of the wrong shape, or a body sent without a JSON `Content-Type`; a body that is not JSON at all is the framework’s `EMC0028`, reference `Body`)
`EIN0010`	unknown or foreign quote
`EIN0051`	a store read, the existing-order lookup included, was unavailable
`EIN0080`	rate limit

For a quote that has no order yet, checked in this order:

Code	When
`EIN0005`	quote expired: the first registration came at or after `expiresAt`
`EIN0006`	the configuration the quote ran under was superseded
`EIN0007`	re-approval or artifact build failed; every OIF-lane quote fails re-approval (known issue)
`EIN0010`	a `create` winner’s `artifactHash` mismatch, or any signature problem

All four come after the user’s transaction was sent: never re-quote because of one (see Behavior). The gateway’s own refusals — a refused credential, a route not open to it, a rate limit, the hub unreachable or too slow — can come back from every route, with an EPX code and a real HTTP status (Errors — gateway codes); EIN0049 (internal, scrubbed) can come back from any route.

Example

curl -sS -X POST https://proxy-api.infinimesh.net/v1/order \
  -H "x-api-key: $HUB_API_KEY" \
  -H "X-Infinity-Subject: user-42" \
  -H 'Content-Type: application/json' \
  -d '{"quoteRequestId":"01M34FSW4R9F2C4E7A1B3D5F80","quoteId":"b9760d500009ec356eb2fc720c32cb77b8b0420a8e2b2deb6a97ce63ba64fb58","artifactHash":"leaf:v1:5c70e8deaaac78819757d29073bcc8dbdb299da6016a35e1e3017569a1202a40","signature":"<personal_sign over signIntent>","signer":"0xf39Fd6e51aad88F6F4ce6aB8827279cffFb92266","scheme":"eip191"}'

Response

Illustrative values; formats follow the Response table. The ids are the example world’s quote, an oif-escrow-gasless quote that completes through POST /order/openfor: sent here first, it would be refused EIN0007 (known issue). The answer below is the idempotent repeat once its openFor order exists — that order’s ack (orderId is the openFor hubOrderId, createdAt its submittedAt), whatever signature fields the repeat carries. A create winner’s own registration answers in the same shape.

{
  "success": true,
  "request_id": "2f304152-6374-45af-9a0b-1c2d3e4f5061",
  "data": {
    "orderId": "a1c662328ee36c035986071fdca2997c167288c9da362f7d540ff102dfedf4c2",
    "quoteId": "b9760d500009ec356eb2fc720c32cb77b8b0420a8e2b2deb6a97ce63ba64fb58",
    "createdAt": "2026-09-22T12:00:20Z",
    "status": "CREATED"
  }
}

// client: your InteropClient (see /infinity-interop/sdk/installation)
const created = await client.api.createOrder({
  quoteRequestId: q.quoteRequestId, quoteId: q.quoteId,
  artifactHash: q.disclosure.signableHash,
  signature: sigIntent, signer: address, scheme: "eip191",
});

Get started

Core concepts

Resources

API reference

SDK

SDK reference

Request

Request body

Response

Behavior

Errors

Example

Response

See also

​Request

​Request body

​Response

​Behavior

​Errors

​Example

​Response

​See also

Request

Request body

Response

Behavior

Errors

Example

Response

See also