StarStock API

Base URL: https://api.starstock.app/api/v1

• In a browser: open any link on this page, e.g. /search?q=tritanium.
• In Google Sheets: paste into cell A1 of an empty tab to load the whole market:

  =IMPORTDATA("https://api.starstock.app/api/v1/items.csv")

• In code: send a plain GET request. Responses are JSON and CORS is open, so it works from any website, bot or script.

  curl "https://api.starstock.app/api/v1/items/41000000000"

sell = the cheapest sell order (what you pay to buy now). buy = the highest buy order (what you get selling now). Jita prices are fields named cheapest_*; the best price in all regions is everywhere_*. Items are identified by type_id (Tritanium is 41000000000; find others with search).

Google Sheets

Load the market into an empty tab named Market (cell A1):

=IMPORTDATA("https://api.starstock.app/api/v1/items.csv")

Then look up a price by name from any other tab (A2 = item name). Column D is sell, E is buy, F is units for sale:

=INDEX(Market!D:D, MATCH(A2, Market!B:B, 0))

One item without a lookup tab (row 2, column 2 = sell; use column 3 for buy, 4 for units for sale):

=INDEX(IMPORTDATA("https://api.starstock.app/api/v1/items/41000000000.csv"), 2, 2)

Google refreshes IMPORTDATA on its own schedule (about hourly). Use one whole-market tab rather than many single-item formulas.

Excel

1. Data → Get Data → From Other Sources → From Web, paste the link below, choose Anonymous if asked, then Load.

   https://api.starstock.app/api/v1/items.csv

2. To keep it current: Data → Queries & Connections, right-click the query, Properties, tick Refresh every 10 minutes.
3. Look up a price: =INDEX(items[cheapest_sell], MATCH(A2, items[name], 0)) (use the table name shown under Table Design).

Add ?scope=all to any CSV link for all-regions prices instead of Jita (the price columns are then named best_sell and best_buy).

Items with current prices, A to Z.

GET /items?ids=41000000000,51000000006&live=1

One item: current prices plus time-weighted averages over a window, and its estimate (see fields).

{ "ok": true, "item": { "type_id": 51000000006, "name": "Rich Veldspar",
  "cheapest_sell": 28, "cheapest_buy": 25, "everywhere_sell": 26, "everywhere_buy": 25,
  "average_sell": 29.43, "average_buy": 25.4, "vol_jita": 4645133, "activity": "active", ... },
  "estimate": { "price": 26, "source": "market" } }

Price points for one item, oldest first. A point is recorded when the price or units for sale changed. Takes window like above.

• ts is Unix time in seconds. Points older than ~30 days are merged into one per day (at 00:00 UTC) and may carry avg_* (that day's time-weighted average) and close_* (the price at the end of the day).
• The first point may have "carried": 1: the price already in effect when the window opened.

Daily history files: every item's price points for one UTC day in one download. For the whole market's history, use these instead of one /history request per item. days = the dates with a file, newest first (about the last 4 weeks; a new day is added after 01:00 UTC).

{ "ok": true, "days": ["2026-10-11", "2026-10-10", ...],
  "fields": ["type_id", "ts", "cheapest_sell", ...], "url": "/api/v1/history/day/{date}" }

One day's file ({date} = YYYY-MM-DD). points is a list of arrays in the order of fields: type_id, ts (Unix seconds), cheapest_sell, cheapest_buy, everywhere_sell, everywhere_buy, highest_sell, everywhere_highest_sell, vol_jita, vol_all. Like /history, a point is recorded only when something changed, so an item with no point that day kept its earlier price. A finished day never changes, so a file only needs downloading once.

{ "ok": true, "day": "2026-10-11", "fields": [...],
  "points": [[51000000006, 1791676800, 28, 25, 26, 25, 31, 31, 4645133, 9022871], ...] }

The order book: sell (cheapest first) and buy (highest first), each { price, qty, ss, rg, j } = price, quantity, solar system id, region id, and j: 1 if the order counts as Jita. fetched_at = when the book was read.

The game shows at most ~220 sell orders per item, so very deep items (Tritanium, PLEX) are cut off at the expensive end. The buy side is complete. A book is re-read when the price moves, and at least every 24 hours.

Items by name, best match first. q needs at least 2 characters; limit 1 to 100 (default 30). total = how many items matched. categories = the market categories the matches are in (path, count), biggest first; add cat={path} to keep only that category.

Items whose price changed most recently. limit 1 to 150 (default 150).

The market's category tree, with the number of items in each category and its path.

Every item in one compact response (about 1.7 MB), with short keys:

The whole market, or one item, as CSV. Columns: type_id (whole market only), name, path (whole market only), cheapest_sell, cheapest_buy, volume (units for sale), last_updated, estimated_price (the estimate price; empty = none). ?scope=all switches to all-regions prices; ?ids= (up to 200) limits items.csv to those items.

Number of items tracked and when data last came in (last_updated).

Every open public contract, newest first (about 600 KB). ?type_id= keeps contracts that include that item; ?id= returns one contract.

{ "ok": true, "count": 591, "contracts": [ { "contract_id": 26259894, "type": 1,
  "seller": "07fcc10f48f0", "price": 160000000, "date_expired": 1790757677,
  "start_solar_system_id": 30004381, "items": [ { "t": 61999001320, "q": 1, "r": 0, "f": 0 } ], ... } ] }

Contracts completed (accepted) in the last 60 days, newest first. sold_at = when StarStock saw it completed.

Contracts that ended without a sale in the last 60 days (ended: expired or removed), newest first. Only contracts with up to 12 item lines that include at least one item with no market price are kept.

Planets matching at least one filter. With resource, the planets with the most output of it come first; otherwise they are in system order.

GET /planets?resource=Lustering%20Alloy&region=The%20Forge&limit=1
{ "ok": true, "total": 409, "planets": [ { "name": "Fuskunen III", "planet_type": "Gas",
  "system_id": 30000199, "system": "Fuskunen", "security": 0.2, "true_security": 0.23,
  "constellation": "Mivora", "region": "The Forge", "jumps_from_jita": 15, "wormhole": false,
  "output_bonus": 1.8, "resources": [ { "type_id": 42001000000, "name": "Lustering Alloy",
  "richness": "Perfect", "output": 29.74 }, ... ] } ] }

Every system on the star chart (about 1.4 MB), with regions, constellations, faction names and NPC station names. x, y = position on the 2D chart; ly = 3D position in light-years. gates = the systems its stargates lead to. faction_id 0 = none. off_chart_stations = stations in systems the chart doesn't draw.

{ "ok": true, "regions": [ { "id": 10000001, "name": "Derelik" }, ... ],
  "constellations": [ { "id": 20000001, "name": "San Matar", "region_id": 10000001 }, ... ],
  "factions": { "500001": "Caldari State", ... },
  "systems": [ { "id": 30000001, "name": "Tanoo", "region_id": 10000001, "constellation_id": 20000001,
    "true_security": 0.8583, "faction_id": 500007, "x": 0.01896, "y": -0.07305, "ly": [-9.3556, 4.4785, -4.7051],
    "stations": [ "Tanoo IV - Trust Partners Trading Post", ... ], "gates": [ 30000003, ... ] }, ... ],
  "off_chart_stations": [ { "name": "...", "system": "0IRK-R" }, ... ] }

Each region's outline on the 2D chart, as lists of [x, y] points in the same coordinates as /starmap/systems (about 700 KB).

{ "ok": true, "regions": { "10000001": [ [ [0.1308, -0.0963], [0.1336, -0.0938], ... ] ], ... } }

The latest reading of every layer.

{ "ok": true, "received_at": "2026-10-10T21:57:26.992Z", "layers": {
  "kills1h": { "at": "2026-10-10T21:57:26Z", "data": [ [30000195, 11], ... ] },
  "sov": { "at": "2026-10-10T19:40:35Z", "data": { "30000208": [0, 1000022908, 2000000675], ... } }, ... } }

Days with a saved daily copy of the layers.

{ "ok": true, "dates": [ "2026-10-07", "2026-10-08", ... ] }

One day's copy (YYYY-MM-DD, UTC), same shape as /starmap/live plus date. HTTP 404 for a day with no copy.

Pirate strongholds destroyed in each sov owner's systems (the Rat Board). The owner is the system's sov alliance, else its sov corp.

{ "ok": true, "today": "2026-10-10", "dates": [ "2026-10-09", "2026-10-10" ], "board": [ { "id": 2000000572,
  "kind": "alliance", "ticker": "SOS", "name": "...", "logo": [41, 20, 21, 1, 19, 19, 1], "members": 2602,
  "totals": { "today": 10645, "d3": 22323, "d7": 22323, "d30": 22323, "all": 22323 },
  "corps": [ [ "THDG", "...", [10, 5, 7, 19, 32, 19, 56, 0], 95, 1000023717 ], ... ] }, ... ],
  "corp_dates": [ "2026-10-11" ], "corp_board": [ { "id": 1000011193, "ticker": "THD", "name": "...",
  "logo": [10, 5, 7, 19, 32, 19, 56, 0], "members": 331, "alliance": [ 2000000572, "SOS", "..." ],
  "totals": { "today": 1229, "d3": 1229, "d7": 1229, "d30": 1229, "all": 1229 } }, ... ] }

totals: today so far, the last 3, 7 and 30 days (including today), and every day recorded (dates). corps (alliances only): member corps holding its systems now, as [ticker, name, logo, members, id].

corp_board: every corp holding sov systems (alliance members included), counting the systems it holds, over the days in corp_dates (per-corp counts start 2026-10-11). alliance: [id, ticker, name], or null for a corp without one.

top (every row): its 3 systems with the most strongholds destroyed per period, { "today": [[system, count], ...], "d3", "d7", "d30", "all" }, over the days in sys_dates (per-system counts start 2026-10-11).

A route between two systems, worked out like the Star Chart's route finder. Systems and regions can be names (any case) or ids; lists are comma separated.

/starmap/route?from=Jita&to=Amarr&safest=1&ship=Rifter

{ "ok": true, "from": { "id": 30000142, "name": "Jita", "region": "The Forge" },
  "to": { "id": 30002187, "name": "Amarr", "region": "Domain" },
  "jumps": 9, "low_sec": 0, "null_sec": 0, "ship": "Rifter", "travel_time_s": 304,
  "steps": [ { "to": { "id": 30002187, "name": "Amarr" }, "via": "gate", "jumps": 9 } ],
  "route": [ { "id": 30000142, "name": "Jita", "region": "The Forge", "security": 0.9, "via": null },
    { "id": 30000144, "name": "Perimeter", "region": "The Forge", "security": 1, "via": "gate" }, ... ],
  "filters": { "safest": true, "sec_min": null, "sec_max": null, "avoid_systems": [], "avoid_regions": [],
    "ansiblex": false, "cyno_range": null },
  "star_chart_url": "https://starstock.app/starmap?route=30000142-30002187&safe=1" }

route: every system in order, with its security as the chart shows it (rounded to 0.1) and how it is reached: via gate, ansiblex or cyno (null for the start). steps: the autopilot steps, each run of stargate jumps as one step and each Ansiblex or cyno jump as its own. low_sec / null_sec: systems passed through (not the start) at 0.1 to 0.4 / 0.0 and below. travel_time_s: seconds, from the game's own formula with the ship's base stats (no skills), starting 30 AU from the first gate like the game; null without a ship or when the route has an Ansiblex or cyno jump. live (only with ansiblex or cyno): the at time of the layer used, null when none is newer than 12 hours. star_chart_url opens the same route on the Star Chart. The game's autopilot picks its own way between steps.

HTTP 400 for a missing or unknown system, ship or region, or a bad number; 404 when no route exists (with the filters given). Both answer { "ok": false, "error": "..." }.

Items

Contracts

Planets

• Burst limit: at most 10 requests per 10 seconds per IP address. Over that you get HTTP 429 for 10 seconds. Spread requests out (about 1 per second keeps you well clear).
• Rate limit: about 300 requests per minute per IP address. A single item or its history counts as 3 (7d), 5 (30d), 8 (90d), 12 (1y) or 15 (all); an order book or item CSV counts as 3. Over that you get HTTP 429 with a Retry-After header (seconds) and reset_at (Unix time in milliseconds).
• Caching: responses are cached for 60 seconds (item history for 3 hours, daily history files for a day), so polling faster returns the same data. /items, /categories, /catalog.json and the CSVs are built from a list refreshed about every 20 minutes; single items, /search and /recent are live.
• Bulk data: for the whole market use one /catalog.json or /items.csv request, and for history the daily files at /history/days, not one request per item.
• Daily limit: 2,000 single-item requests (/items/{type_id}, its /history and /orders) per network per UTC day (IPv4 /24, IPv6 /64). Some cloud hosts share one count of 500 for all their addresses. Cached answers don't count. Over that you get 429 with a Retry-After header until 00:00 UTC.
• Daily pause: if StarStock's daily database budget is nearly used up, item history and item CSV return 503 with a Retry-After header until 00:00 UTC. API requests (/api/v1) for single items, their history and CSV pause earlier, at 75% of the budget, so the site keeps working; the bulk endpoints and order books keep working.
• Errors: { "ok": false, "error": "..." } with a 4xx or 5xx status. Unknown items and addresses return 404.

Use of the API is covered by the terms. Questions or feedback: the StarStock Discord, linked from starstock.app.