Search
⌘K
Orderbook API
API version: All versions
Introduction
Quickstart
Methods
Include a limit order to the 1inch limit orders database POST
Get order by the specified order hash GET
Get orders count by specified filters GET
Get fill/cancel events related to the specified order GET
Get limit orders history by address (Cursor Pagination) GET
Get all limit orders with cursor pagination GET
Get orders by address with cursor pagination GET
Get all orders fill/cancel events with cursor pagination GET
Get all active orders which have permit for the specified wallet address and token GET
Get calculated making amount on trading pair by provided amount GET
Get unique active token pairs with cursor pagination GET
Get market price for a token pair GET
Migration
Migration V3 - V4
SDK
Introduction
Querying the Orderbook
Advanced usage
Docs·APIs·Orderbook API·Introduction

Introduction

1inch Orderbook API is using the 1inch Limit Order Protocol, which is a set of smart contracts that can work on any EVM-based blockchains. Key features of the protocol are extreme flexibility and high gas efficiency.

Orderbook

An orderbook is a trading mechanism where users create fixed-price orders for tokens, specifying both the execution price and an expiration condition that limits how long the order remains valid. For example, you can put up 2 WBTC tokens for sale at the price of 82,415 DAI tokens valid for 7 days.

The 1inch Limit Orders Protocol provides a rich set of tools for flexible and professional trade management:

  • Partial fill Orders can be filled in multiple steps without requiring full execution at once.
  • Predicates Conditional execution logic (e.g. price bounds, time constraints, external state checks).
  • Single cancellation Cancel a specific order by its unique hash.
  • Batch (bunch) cancellation Invalidate multiple orders efficiently in a single action.
  • Fullness check Ensure the order is filled exactly as specified, preventing over- or under-fills when required.
  • Validation Custom on-chain validation logic to control whether an order can be executed.

To enable efficient market making, RFQ orders are used, benefiting from a special optimization that avoids high gas costs during execution.

Limit order execution

1. Order placement

Users place limit orders. Each order is cryptographically signed and remains off-chain until executed.

2. Order discovery

Anyone can fetch these signed orders using the 1inch Orderbook API to execute trades by submitting them on-chain.

3. Order execution

To execute an order, the signed order is submitted to the smart contract's fillOrder method. See the latest contract addresses in Limit Order SDK.

Both the buyer and seller must approve the 1inch Limit Order Protocol to transfer their tokens.

Supported tokens standards

  • ERC-20
  • ERC-721
  • ERC-1155

Other token standards can be supported via external extensions.

For workloads that require higher RPS, expanded quotas, or sustained performance, explore the available paid plans on the pricing page. For organizations with significant trading volumes or advanced requirements, complete this application to explore tailored Enterprise options.

Supported Chains

Supported Chains Chain ID
Ethereum 1
Base 8453
Binance 56
zkSync 324
Gnosis 100
Optimism 10
Polygon 137
Linea 59144
Sonic 146
Unichain 130
Arbitrum 42161
Avalanche 43114

More resources

Did you find what you need?