Prices
Base price, AI price, and current player price. The player price is always the higher of the AI price and the highest active player buy request; your own buy requests are not included. Without a higher player price, the AI price is used. Excel contains a single worksheet with the price table. The limit is 30 requests per minute per API key; the reverse proxy may throttle earlier.
Personal account data
One unique API key per account with the account:read scope. The same complete key is used in the finished URL for all seven account topics. The limit is 30 requests per minute. Mines, factories, fields, water buildings, and power plants use stable externalRef values; exports are capped at 100,000 mines, 10,000 factories, 50,000 active jobs, 256 inventory rows, 10,000 fields, 10,000 water buildings, 10,000 power plants, 25 MiB JSON, and 64 MiB XLSX.
Retrieve data
The finished URL contains your complete API key in plain text. Do not share it publicly. Without input, the generator shows only a non-working example key.
Excel: Copy the link and paste it under Data → Get Data → From Web. Prices, Mines, Factories, Inventory, Agriculture, Power, Trade, and Loans have one worksheet each when requested individually, with no metadata worksheet. The price export contains the basePrice, aiPrice, and playerPrice columns directly in the table. A combined account export contains one worksheet per selected topic. Other programs can use the same generated link as a normal web address.
Mines · 1 credit
All owned mines with resource, level, quality, exact coordinates in plain text, condition, optimisation and confirmed stored quantity.
/v1/account/mines.jsonFactories · 1 credit
All owned factories with level, operating ratio, current job, status, quantities and finish time.
/v1/account/factories.jsonInventory · 1 credit
Confirmed general inventory for every item, including the current level of each item storage. External requests never trigger production or collection.
/v1/account/inventory.jsonAgriculture · 1 credit
Agriculture V2: fields and water buildings share a flat list with recordType=field or recordType=waterBuilding, also in a single Excel worksheet. Field name, product, persisted status, cycle duration, expected base output per cycle, fertilizer toggle, and persisted condition; water buildings include kind and radius. No field quality or seed returns.
readyAt is a stored schedule timestamp, not a guarantee of harvest readiness. expectedOutputPerCycle is not confirmed inventory and excludes fertilizer and other bonuses. The fertilizer toggle does not confirm supply. Requests do not recalculate elapsed cycles, life decay, or harvests.
/v1/account/agriculture.json/v1/account/agriculture.xlsxPower · 1 credit
One row per owned power plant with kind, level, persisted lives, and operationalRatio. nominalPowerKw and nominalFuelPerHour describe nominal output and fuel use by kind and level, not actual current output. Fuel-less plants have no fuel item and nominal fuel use 0.
No complete energy balance or runtime forecast. Agriculture and power include no coordinates, account, authentication, or device data. Campus is not supported.
/v1/account/power.json/v1/account/power.xlsxTrade · 1 credit
Only your own open, unexpired buy requests (recordType=buyRequest, status=OPEN, expiresAt > generatedAt), followed by retained own transactions (recordType=transaction, side=BUY/SELL) within the trailing 30-day window. No sell offers. Each group is ordered by creation time ascending with a stable internal tie-break.
remainingQuantity is the stored remaining buy-request quantity; the original quantity is no longer retained, so quantity=null. Transactions contain executed quantity, but their remainingQuantity, status, expiresAt and updatedAt are null. unitPrice is the stored price. total is not recalculated: for requests it is the remaining reserved trade value excluding separately stored tax, not the original order total; for transactions it is the recorded gross trade value, not net payout after garnishment or tax-inclusive account cash flow.
Single-topic JSON includes history: {from, to, days: 30, completeness: "not-guaranteed"}. from is exactly 30 × 24 hours before generatedAt; to equals generatedAt, with inclusive boundaries. This describes transactions only, not current requests. Retention/deletion may remove rows: not a guarantee of complete 30-day or lifetime history. Combined JSON with trade includes history: {trade: {from, to, days: 30, completeness: "not-guaranteed"}}; without trade, history is absent.
Independent limits: 10,000 buy requests and 10,000 transactions, at most 20,000 rows total. Overflow returns 413; data is never truncated. Quantities use item, unitPrice uses IC/item, and total uses IC.
Ordered JSON fields / Excel columns
recordType, externalRef, side, itemType, name, status, quantity, remainingQuantity, unitPrice, total, expiresAt, createdAt, updatedAt/v1/account/trade.json/v1/account/trade.xlsxLoans · 1 credit
Your borrowed loans (recordType=borrowedLoan), own funding contributions including refunded contributions (funding), then strict legacy single-lender loans (legacyLending). Legacy rows require you to be the lender, source=PLAYER, fundingMode=LEGACY_SINGLE, and no funding records at all for that loan. Each group is ordered by creation time ascending with a stable internal tie-break. All stored statuses are included, including pending, cancelled and paid. source and status come from the related loan, not a calculated funding status.
principal, interestAmount, totalRepayable, paidAmount and remainingAmount are stored amounts in IC. Funding rows contain only your contribution amounts, never the other borrower's whole-loan amounts. Borrowed rows contain your debt; strict legacy rows contain the sole-lender loan amounts. Unknown amounts are null, not invented zero. These are accounting fields, not certified current collectible balances: pending contributions may be escrow reservations and refunded rows retain amounts; inspect refundedAt and status.
dueAt is the stored loan due date, possibly provisional for pending requests. No installment amount, next installment date or inferred lateness promise; elapsed time never promotes status to OVERDUE. For contributions, fundedAt is the contribution timestamp, not certification of whole-loan disbursement or activation. paidAt and refundedAt are stored timestamps or null; loan rows always have refundedAt=null. createdAt/updatedAt belong to the originating record.
At most 10,000 borrowed loans, 10,000 own contributions and 10,000 strict legacy loans, independently capped; 30,000 rows total. Overflow returns 413, never truncated.
Ordered JSON fields / Excel columns
recordType, externalRef, loanExternalRef, source, status, principal, interestAmount, totalRepayable, paidAmount, remainingAmount, dueAt, fundedAt, paidAt, refundedAt, createdAt, updatedAt/v1/account/loans.json/v1/account/loans.xlsxTrade and loan format
JSON and Excel use the same flat rows with identical column order. Excel has exactly one worksheet per topic: Handel / Kredite in German and Trade / Loans in English, with no metadata worksheet. Credit cost and remaining balance are also returned in response headers. Every decimal quantity and monetary amount is a string with exactly six decimal places; missing or inapplicable values are explicit null. Timestamps use UTC ISO-8601. Existing 25 MiB JSON / 64 MiB XLSX limits also apply.
externalRef is stable, opaque and separated by record purpose; loanExternalRef identifies the related loan and equals externalRef for loan rows. Only trade name is a localized item label; machine fields and loan rows do not change with language. No participant names/IDs, coordinates, risk, events, authentication or device data. One shared read-only snapshot across selected topics; no settlement, expiry processing, garnishment or disbursement. The OpenAPI schema documents types, nulls and limits.
Billing
A combined request adds only distinct topics. Format, row count and detail fields do not change the cost. Agriculture counts as one topic despite its two row types. Without include, /v1/account/export.json or .xlsx still defaults to mines,factories,inventory for 3 credits. New topics require explicit selection. The original five: /v1/account/export.json?include=mines,factories,inventory,agriculture,power for 5 API credits (also pass the same complete key as key; .xlsx is available too). All seven: /v1/account/export.json?include=mines,factories,inventory,agriculture,power,trade,loans for 7 API credits (also .xlsx; add the complete key). Trade and loans each cost 1 credit regardless of record type. include trims surrounding topic whitespace, normalizes case, ignores empty comma tokens and duplicates; at least one valid topic is required. Invalid or internally failed requests are not charged. The first API activation includes a one-time 5 API credits; key rotation or replacing the key grants no additional credits. Further packages of 500 API credits can be purchased repeatedly in the in-game shop.
Errors
400invalid filter, topic, language, or request ID401missing or invalid key402insufficient API credits403missing scope409request ID already used413export exceeds a size limit429rate limit reached500internal error; reserved credits are refunded automatically
Security
- The API key is shown once after activation or rotation.
- The generated URL contains the key in plain text and must remain as private as the key itself.
- Only a cryptographic hash is stored on the server.
- Account responses are never cached.
- Account endpoints are read-only and never run sync, AutoCollect or settlement.
- Manage your key and credits at user.industrygo.de.