TILLA Data API
Three years of market datapoints and derived series, hashed as they land.
Fork copies the collection into your workspace, without the publisher's secrets, so you can add your own key and send requests. Star saves it to your starred APIs (Account › Marketplace) and helps others find it.
Overview
Three years of market datapoints and derived series, hashed as they land.
Endpoints 37
- GETthis index - endpoints, auth, formats, tiers
/ - GETthe same index
/v1 - GETthe same index
/v1/ - GETliveness check
/v1/ping - GETtier catalog: price, history, limits, the hook
/v1/tiers - GETthe newest 1min label and the tiers served
/v1/status - GETthe newest label of every lane, every layer
/v1/health - GETEVERY CALL, READY TO PASTE: method, URL for ?tier=, auth, what it returns, and every error - ?format=json|csv (a sheet)
/v1/calls - GETeverything your tier can do: every call with its ready URL (json, or ?format=csv)
/v1/:tier/calls - GETthe free samples of every tier, no key
/v1/samples - GETone tick of everything a tier holds: {tier}.db (SQLite), {tier}.csv (a sheet), {tier} (JSON at a glance)
/v1/sample/:name - GETwhat your tier holds (?layer=&lane=; ?tier= previews a lower tier)
/v1/inventory - GETyour plan and your budgets right now
/v1/usage - GETraw window: ?series=a,b&start=&end=&limit=&format=json|csv|ndjson|parquet
/v1/:tier/raw/:lane - GETderived window, the same parameters
/v1/:tier/derived/:lane - GETthe node (max and above), the same parameters
/v1/:tier/node/:lane - GETTHE DEEP HISTORY, lane hour: hourly raw prices from each market's first bar (FX 2002, crypto 2017, US stocks 2020) to 2023-08-10, no history floor; the same series names and parameters as raw/hour
/v1/:tier/deep/:lane - GETBULK: the whole window in one streamed request, csv|ndjson|parquet, hashed and recorded (pro and above)
/v1/:tier/export/:layer/:lane - GETTICK: every series your key is sold, on every clock lane that closed at a boundary, in ONE answer (?at=YYYY-MM-DD HH:MM, default the minute just closed; ?lanes=raw/1min,derived/5min to ask again for lanes still writing). Ask once a minute and you have the whole tier, live
/v1/:tier/tick - GETCHANGES: every cell the base repaired, filled or re-walked since ?since= (its hourly audit, 2-hourly sweep and heal, day close, derived rewinds) that your key holds, with its value now - apply them and your copy heals when ours does; pass `until` back as the next since
/v1/:tier/changes - GETRESUME: every series your key is sold on one lane, every bar from ?since= to now, streamed in one request (ndjson|csv|parquet) - fill the gap since you last stopped, then tick
/v1/:tier/resume/:layer/:lane - GETevery main market: its category, its related markets, how many series each tier holds of it, its lanes, and its call
/v1/markets - GETONE MARKET and everything of it your tier holds, on one clock: ?lane=1min&layer=raw|derived|all&related=1 (its ETFs, miners, sister pairs ...)&period=6m; 200 columns an answer, ?offset= walks the rest
/v1/:tier/market/:subject - GETBULK: your whole window straight from the database - every lane your tier holds, each with its resume url (Parquet, csv or ndjson, streamed); ?markets=crypto|stocks|fx|macro|<ids> narrows it to those markets
/v1/:tier/bulk - GETa prebuilt Parquet file by its sha256 - none are published today (404); take the resume urls /bulk lists
/v1/:tier/bulk/file/:sha - GETLIVE: finished bars as they land, SSE (?layer=&lanes=&series=&since=; Last-Event-ID replays)
/v1/:tier/stream - GETlegacy, kept for existing scripts - use /v1/{tier}/raw/{lane}: ?series= (or cols=)&start=&end=&limit=&format=&table=
/v1/data - GETlegacy, kept for existing scripts - use /v1/{tier}/tick: the newest row of ?series= (or cols=) at ?table=
/v1/latest - GETlegacy, kept for existing scripts - use /v1/{tier}/resume/{layer}/{lane}: everything from ?since=, paged with next_start
/v1/sync?since=string - POSTa free key, no account, one per address per day
/v1/demo_key - POSTself-serve free key (signed-in session)
/v1/free_key - POSTyour key; ?peek=1 check without minting, ?rotate=1 replace, ?claim=1 show a just-bought key once
/v1/my_key - POSTstart a subscription (or the portal if already paid)
/v1/checkout - POSTStripe billing portal (manage / cancel)
/v1/portal - POSTan enterprise lead
/v1/enterprise_inquiry - POSTa support ticket: name, email, topic, message - it reaches the founder inbox
/v1/contact - POSTStripe events (signature-verified)
/v1/stripe_webhook
API details
- Base URL
https://api.tillacrypto.com- Authentication
- An API key in the X-API-Key header
- Operations
- 37 operations on 37 pathsGET 29POST 8
- Description format
- OpenAPI 3.0.3, API version
3.0 - Links
- OpenAPI document
- Listed from
- Tillacrypto's published OpenAPI description
How to test the TILLA Data API in Swastik Codes
- Open the APISelect “Fork & run in Swastik Codes” on this page. Sign in or create a free account if asked.
- Fork it into your workspaceChoose a workspace. You get your own copy of the TILLA Data API collection, without the publisher's secrets.
- Add your credentialsThis API uses an API key in the X-API-Key header. Add yours in the collection's variables or an environment; the requests already reference it.
- Send a requestPick an endpoint, for example “this index - endpoints, auth, formats, tiers” (GET /), and press Send. Check the response, add tests and run the whole collection with the runner.
Frequently asked questions
What is the TILLA Data API?
Three years of market datapoints and derived series, hashed as they land. It is listed under Finance & banking and has 37 endpoints.
Who publishes the TILLA Data API?
It is listed from Tillacrypto's public API description (an OpenAPI document), not published by Tillacrypto on Swastik Codes. Anyone who controls tillacrypto.com can claim the profile by adding a DNS TXT record.
What is the base URL of the TILLA Data API?
Requests go to https://api.tillacrypto.com. Endpoint paths are added to this base URL.
How do I authenticate with the TILLA Data API?
With an API key in the X-API-Key header.
How many endpoints does the TILLA Data API have?
37 operations on 37 paths (29 GET, 8 POST).
Is forking the TILLA Data API free?
Yes. Forking copies the collection into your workspace for free. It has been starred 0 times and forked 0 times.