How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

M 0 Order API

The Order API from M 0 — 3 operation(s) for order.

M 0 Order API is one of 5 APIs that M 0 publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Order. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, and an API reference.

This API exposes 3 operations across 3 paths, and defines 12 schemas. It is described by OpenAPI 3.0.1, at version 1.0.

Requests are made against 4 base URLs: https://gateway.m0.xyz/v1/orchestration, https://gateway.stage.m0.xyz/v1/orchestration, https://gateway.dev.m0.xyz/v1/orchestration, http://localhost:5600.

3 operations 3 paths 12 schemas 2 GET1 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.0.1
API Version
1.0
Base URL
https://gateway.m0.xyz/v1/orchestration
Authentication
API Key
Resource Areas
1

Authentication & Security 1

M 0 Order API declares 1 security scheme for authenticating requests. An API key is passed in the header as x-api-key (ApiKeyAuth).

Paths & Operations 3

Across 3 paths, the API surfaces 3 operations — 2 GET, 1 POST. Each is listed below with its method, path, parameters, and response codes.

Order 3
POST
/orders/{originChain}/{orderId}/cancel
Build a cancel transaction for an existing limit order. The returned TransactionPayload carries its own chain (and chainId for EVM payloads) indicating where the transaction must be broadcast: Same-c…
order_cancelOrder 2 params body → 200400404409500
GET
/orders/{originChain}/{orderId}
Get full on-chain state plus indexer enrichment for a single order. Error responses Errors return commons.ErrorBody ({ code, message, requestId }); branch on code, not the HTTP status. | Status | cod…
order_getOrder 2 params → 200400404
GET
/orders
List orders with optional filters
order_getOrders 6 params → 200

Schemas 12

The contract defines 12 schemas that model the data the API accepts and returns. The most detailed are Order (24 properties), OrderSummary (20 properties), Fill (6 properties), EvmPayload (5 properties). Each schema is shown below with its type and property counts.

SvmPayload
object
2 properties 2 required
EvmPayload
object
5 properties 5 required
CancelOrderParams
object
Optional body for the cancel endpoint.
1 property
OrderStatus
string
OrdersResponse
object
4 properties 4 required
TransactionPayload
Order
object
Full order state returned by the detail endpoint. On-chain fields are authoritative; indexer-only fields (openTx, fillCount, fillReportCount, resolvedAt, fills…
24 properties 19 required
Fill
object
A single fill event recorded by the indexer for an order. An order may have multiple fills when filled by multiple solvers or in multiple transactions; ordered…
6 properties 6 required
Chain
string
ErrorCode
string
Stable machine-readable identifier for an API error. Each value corresponds 1:1 to an error type (and to one responses entry in the OpenAPI spec). Branch on th…
ErrorBody
object
Standard error response body. Every error response from this API returns this shape.
3 properties 2 required
OrderSummary
object
Compact order shape returned by the list endpoint. Sourced from the indexer-fed DB, so on-chain-only fields (nonce, recipient, version) are not included. Use g…
20 properties 19 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

m-0-order-api-openapi.yml Raw ↑

Other APIs M 0 publishes across the network.

M0 Protocol API
M 0 Permit API
M 0 Quote API
M 0 Topology API
Where this information came from

This is an independent, third-party profile of M 0 Order API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.