Skip to content
Aggre
Get an API key
Early access

Market candles and statutes, behind one API.

Aggre is a data bank with a single keyed HTTP API. The first release serves exchange candles and the current text of laws from official sources. Every response says where it came from, how fresh it is, and under what terms you may use it.

Get an API key Read the API docs

Sign in with Google, GitHub or Orbbit; your account is created on first sign-in. No payment details are asked for.

One key, two kinds of data
# 24 hourly SOL-USDC candles from OKX spot
curl -G "https://api.aggre.org/v1/finance/market/candles_1h" \
  -H "Authorization: Bearer $AGGRE_API_KEY" \
  -d instrument_id=OKX:SPOT:SOL-USDC -d limit=24

# Five Taiwan statutes, English versions
curl -G "https://api.aggre.org/v1/legal/statutes/instruments" \
  -H "Authorization: Bearer $AGGRE_API_KEY" \
  -d jurisdiction=TW -d language=en -d limit=5

Status at a glance

What is in it

Two kinds of data in the first release, with their limits stated up front. The full list, with status, is on the datasets page.

Market candles

OKX spot, 1-minute, 1-hour and 1-day bars.

  • Confirmed bars only: a bar still forming is never served.
  • A short, curated instrument list (it starts with SOL-USDC and BTC-USDT), not the whole venue.
  • meta.status tells you when the newest bar is stale or the range is empty.
  • One venue collected (OKX spot), no streaming. Perpetual-contract datasets exist as empty routes; nothing flows into them yet.
Market data reference

Legal statutes

8 official sources in the first release, current versions only.

  • Laws and regulations from Taiwan, Japan, the UK, Canada, the EU, the US (CFR), Germany and Australia.
  • Article-level text with the source URL, dates and status of each law.
  • Each record carries license, attribution and restricted.
  • Collected only through official APIs and open data. Singapore and China are not offered yet.
Legal data and licensing

How it works

  1. 1. Sign in and make a key

    Sign in to the console, then create an API key under your personal account or an organization. The secret is shown once.

  2. 2. Call the API from your server

    Send the key as Authorization: Bearer. The API sets no cookies and allows no browser cross-origin calls, so keep the key on a server.

  3. 3. Watch usage and limits

    Each key has a request quota. The console shows usage per key and per day, and GET /v1/whoami returns the same for the key you present.

What you can rely on, and what you cannot yet

Stated in every response

  • meta.status, fetchedAt and dataDate: whether the data is fresh, stale or empty, and when it was read.
  • meta.attribution, meta.licenses and meta.restricted on statute responses, so attribution is not something you have to remember.
  • An x-request-id header on every response and a stable error envelope with machine-readable codes.
  • Usage records hold the method, route template, dataset, status and request id. They hold no IP address and no query text.

Early-access limits

  • Sources are being switched on one at a time. The API's own dataset list is the final word on what has data.
  • No paid plans, no service-level agreement, and no payment flow yet.
  • No history for statutes, no search over them, no streaming, and one trading venue.
  • The not-available list is kept current.

Try it with your own key

Creating an account takes one sign-in. The docs need no account.

Sign in to the console API docsPricing