MineTech Core API
Mining operations, workforce, safety, compliance, inventory, environment, finance and reporting.
MineTech supports two authentication schemes.
API keys (apiKey) — for server-to-server integrations.
Send Authorization: Bearer mt_live_… (or mt_test_… for sandbox). The key
carries its own tenant, so no tenant header is required.
Keys may additionally require request signing. When enabled, send:
x-mt-timestamp: current Unix time in secondsx-mt-signature:t=<unix-seconds>,v1=<hex HMAC-SHA256>
The signed string is {timestamp}.{METHOD}.{path-with-query}.{sha256hex(body)}.
Signatures are accepted within a 300-second window. Signing is on by default for
live keys and off for test keys.
JWT (jwt) — used by the MineTech web and mobile apps.
Not intended for integrations; API keys cannot reach the auth endpoints.
Authentication
- HTTP: Bearer Auth
- API Key: apiKey
MineTech dashboard session token.
Security Scheme Type: | http |
|---|---|
HTTP Authorization Scheme: | bearer |
Bearer format: | JWT |
API key as Bearer mt_live_… / Bearer mt_test_…. Issue keys under Developers → API Keys.
Security Scheme Type: | apiKey |
|---|---|
Header parameter name: | Authorization |
License
Proprietary