Endpoint selection

The public test gateway is https://proxy-api.infinimesh.net/v1. Obtain production access and endpoint details from [email protected]. The direct Infinity Hub service uses /infinity/v1 with its own authentication. Send JSON objects with Content-Type: application/json for POST requests. GET requests have no body. The OpenAPI endpoint returns YAML.

Gateway headers

Send exactly one credential header. Keep the subject unchanged between quoting, submission, and tracking. The subject contains 1–128 characters from letters, digits, ., _, @, +, ~, and -.

Response envelope

JSON responses use a Boolean success field. A successful response contains data. A failed response omits data and contains an errors array.
Each error can include error_code, error_message, error_reference, and error_params. The envelope can also contain message. Inspect the envelope as well as the HTTP status. Keep request_id and the response’s X-Request-Id for support. Do not parse human-readable messages as stable machine identifiers. The direct Infinity Hub service normally returns HTTP 400 for errors, including some retryable errors. Shutdown and admission-limit responses use HTTP 503 with Retry-After. The gateway can return other HTTP statuses for authentication, request limits, or upstream failures. Some transport errors contain plain text instead of a JSON envelope. Use the documented error code to determine retry behavior.

Value formats

Do not convert token amounts to JavaScript floating-point numbers.

Identifier namespaces

quoteId identifies a quoted offer. quoteRequestId identifies the quote round. hubOrderId is Infinity Hub’s durable order alias. The upstream orderId identifies the aggregator’s record. onchainOrderId identifies the contract order. Use the identifier required by each endpoint. Do not assume that an upstream identifier is always a contract identifier. Clients must tolerate additional response fields.