Announced listings and delistings
The listings calendar: what each venue has announced, when it takes effect and where the announcement is. Filter by coin, venue, kind, status, detection source, an effective window and what is new since a time (detected_after); nearest first by default.
Request
- Base URL: https://arbitron.app
- URL: https://arbitron.app/api/v1/listings
- Auth: HTTP bearer
Query parameters
One ticker or a comma-separated list, e.g. BTC,ETH. Case-insensitive.
Keep rows on these venues. One venue or a comma-separated list, spelled as /exchanges spells it, e.g. Binance,Bybit.
Drop rows on these venues. One venue or a comma-separated list, spelled as /exchanges spells it, e.g. Binance,Bybit.
listing or delisting. Default: both.
Exact status as the row carries it, e.g. preopen, newly listed, delisted.
announcement, instruments or diff: how the row was detected. Default: all.
Keep rows effective at or after this time (ISO 8601 UTC).
Keep rows effective before this time (ISO 8601 UTC).
Shortcut: rows effective between now and this many days ahead, 1 to 365. Ignored when from or to is given.
Keep rows first seen after this time (ISO 8601 UTC): what is new since your last poll.
nearest (default: upcoming soonest first, then past most recent first, undated last), effective_asc, effective_desc, detected_desc, detected_asc, coin_asc.
Rows per page, 1 to 500 (Demo: 50). Default 100.
meta.next_cursor from the previous page.
Comma-separated row fields to keep, e.g. exchange,coin,rate_pct; the others are dropped from every row. Unknown names are a 400 that lists the fields.
Response
OK
Changes
No recorded changes to this operation across all 1 revision of this API.