Skip to main content
Omnibook runs a continuous series of 60-second binary markets on the price of BTC. Each round has a strike price; you trade YES or NO on whether BTC closes above it. Contracts settle at 100¢ or 0¢. This API is the same one the Omnibook web app uses. Anything you can do in the browser, a bot can do — with one deliberate exception: API keys cannot withdraw funds.

Authentication

Create a key and sign your first request. Start here.

Your first request

Find the round that is trading right now.

Place an order

Buy YES, understand ticks, retry safely.

API reference

Every endpoint, generated from the OpenAPI spec.

​
Base URL

Every endpoint lives under /v1/.

​
What you should know before you start

Everything is authenticated. There is no anonymous access, not even for market data. You need a key before you can read a price. See Authentication. Requests are signed, not bearer-token. You sign each request with HMAC-SHA256 over the method, target and body. Nothing replayable travels on the wire, and the timestamp window is ±5 seconds. Your key trades your account. A key is bound to the same balance and positions you see when signed in — there is no separate bot account. Bot keys cannot withdraw. Trading and withdrawing are separate scopes, and keys you create only get the former. A leaked key can lose you money through bad trades, but it cannot send your money anywhere. See API keys and scopes. Rounds are short and market_id is recycled. Rounds last 60 seconds and market_id values are reused across rounds. Key your own state on round_number, which is monotonic and never reused.

​
Getting help

Errors carry a stable machine-readable code — see Errors for the full list and what to do about each.