Mining APIs for client applications and data pipelines
The production-ready /api/v1 contract exposes stable payloads, docs, auth, client controls, and the same company and project data that powers the terminal pages.
Mining Companies
Data Points
Projects Tracked
Production API
GET /v1/companies/2523/workspace
Authorization: Bearer <token>
{
"data": {
"companyId": 2523,
"navigation": {
"groups": [
{ "id": "monitor", "label": "Monitor" },
{ "id": "financials", "label": "Financials" },
{ "id": "news-events-filings", "label": "News, Events & Filings" }
]
},
"company": { "id": 2523, "name": "Integra Resources Corp.", "ticker": "ITR" },
"financials": { "cashLiquidityMetrics": [] },
"projects": [
{ "id": 9901, "name": "DeLamar", "economics": {}, "documents": {} }
],
"coverage": {
"views": {
"financials.balance-sheet": { "available": true },
"news-events-filings.regulatory-filings": { "available": true }
}
}
},
"meta": {
"request_id": "req_company_workspace_1",
"as_of": "2026-04-23T12:00:00.000Z"
}
}Start with the enterprise contract and keep every client on the same API
The normalized enterprise API covers companies, projects, documents, extractions, analytics, map, market, stocks, insider activity, AI analyst research, and workspace routes with stable envelopes and Bearer-key access.
The workspace payloads mirror the terminal sidebar, while granular endpoints let engineering teams pull narrower slices for internal tools, data products, and research workflows.
Build on the production API
Mining Terminal client integrations should use the enterprise/api/v1 surface for application development, research systems, internal dashboards, and partner data feeds.
Use the enterprise API when you need a stable customer contract:
- ✓/companies and /companies/:id/* — profiles plus drill intercepts, resources, production, financials, guidance, MD&A, peers, capital structure, and terminal-grade workspace payloads
- ✓/projects and /projects/:id/* — 17,000+ mineral projects with geology, drill collars and intercepts, economics, country risk, and qualified persons
- ✓/documents, /news, and /insider-trades — filings, headlines, and market-moving disclosures tied back to issuers and projects with normalized envelopes
- ✓/analytics/* — screeners, resource rankings, cost curves, footprint analysis, and benchmark workspaces
- ✓POST /v1/ai/analyst — grounded, model-backed research answers with evidence metadata, bounded result rows, and premium credit metering
- ✓/map/*, /country-risk, and /benchmark/* — geographic, sovereign, and cohort comparison context for portfolio workflows
- ✓OpenAPI + client controls — admin-issued keys, request logging, rate limits, quotas, and generated reference docs keep onboarding clean
One mining dataset, one client API
The same curated mining intelligence can power application integrations, research systems, dashboards, and data products through /api/v1. Start with workspace routes for page parity, then add focused endpoint families as the workflow gets more specific.
Documents
Drill Results
Exchanges
Coverage available through /api/v1
The API shapes Mining Terminal intelligence into customer-ready workflows while preserving the underlying depth for research, screening, monitoring, and portfolio systems.
Companies
Comprehensive profiles for 2,300+ publicly traded mining companies across 40+ exchanges worldwide.
Access corporate structure, management, share data, financials, and every regulatory filing—linked to projects and production assets.
Available fields include:
- Company identifiers (ticker, ISIN, CUSIP)
- Exchange listings and trading data
- Corporate structure and subsidiaries
- Management and insider holdings
- Financial statements and ratios
- Market cap and share statistics
Choose the endpoint family that matches the job
Client rollouts should start on the enterprise API.
We keep /api/v1 optimized for productized integration, page parity, research workflows, and data applications so clients do not have to choose between clean payloads and broad mining coverage.
| Workspace Routes | Granular Routes | |
|---|---|---|
| Best for | Page parity, onboarding, full entity context | Narrow pulls, dashboards, data products |
| Interface | Company/project workspace payloads | Company, project, document, market, stock, insider, analytics, map, sector, and AI analyst endpoints |
| Auth model | Admin-issued Bearer keys | Same Bearer-key contract |
| Breadth | Complete visible terminal sections | Focused datasets and filtered collections |
| Recommendation | Start here first | Add as workflows narrow |
Frequently Asked Questions
Common questions about the enterprise API, data coverage, and client rollout.
Mining Terminal serves normalized JSON through versioned `/api/v1` routes with OpenAPI documentation, pagination metadata, request tracing, and rate-limit headers.
Pricing depends on usage profile, seats, and workflow scope. We start every client from the production `/api/v1` contract and size access around the routes, throughput, and support level they need.
Update cadence depends on the data family. Market, filings, and extracted mining datasets are refreshed through the underlying ingestion and review pipelines, and the API surfaces freshness metadata so clients can monitor recency directly from responses.
Yes. Historical availability depends on the data family. We scope `/api/v1` access around the client use case so research, backtesting, and retention needs are covered intentionally.
Evaluation starts with the live `/api/v1` OpenAPI contract and authenticated test access using scoped Bearer keys.
The API uses Bearer keys over HTTPS with `Authorization: Bearer mt_live_...`, plus request IDs, rate-limit headers, quota hooks, and request logging.
Start with workspace routes for page parity, then add granular company, project, document, stock, market, insider, analytics, map, benchmark, and AI analyst endpoints as your integration needs narrower pulls or grounded research answers.
Request API Access
Tell us which production /api/v1 workflows you need, and we’ll help scope the right endpoint coverage.
Get in Touch
Request API Access
Share the application, dashboard, or research workflow you’re building and we’ll recommend the right endpoint families.