Tractian APItractian.com ↗
Access Tractian's hardware specifications and AI detection intelligence via API. Get sensor specs, failure modes, sampling modes, and detection workflow data.
What is the Tractian API?
The Tractian API exposes 2 endpoints covering the full technical profile of Tractian's condition monitoring system. get_hardware_specifications returns over 10 structured fields including sensor measurements, wireless communication bands, battery details, certifications, and supported rotating asset types. get_detection_intelligence returns the AI system's detectable failure modes, detection workflow steps, data sampling modes, spectral analysis tools, and failure lifecycle stages.
No input parameters required.
curl -X GET 'https://api.parse.bot/scraper/8e1272e5-7a90-4693-8a32-927555dab5bb/get_hardware_specifications' \ -H 'X-API-Key: $PARSE_API_KEY'
Typed, relational, agent-ready
A generated client with real types, enums, and the links between objects — the structure a flat JSON response can't carry. Autocompletes in your editor and reads cleanly to coding agents.
- Fully typed · autocompletes
- Objects link to objects
- Typed errors & pagination
Typed Python client. Set up the SDK in your uv project, then pull this API’s typed client:
uv add parse-sdk uv run parse init uv run parse add --marketplace tractian-com-api
uv run parse add --marketplace pulls a pinned snapshot of this canonical API — it won’t change underneath you. To customize it, subscribe and swap to your own copy.
"""Walkthrough: Tractian detection capability SDK — hardware specs and AI detection intelligence."""
from parse_apis.tractian_com_api import Tractian, ParseError
client = Tractian()
# Retrieve the hardware sensor specifications
try:
sensor = client.sensors.get()
except ParseError as e:
print(f"Extraction failed ({e.code}): {e}")
raise
print(f"Sensor: {sensor.sensor_name} ({sensor.sensor_type})")
print(f" Battery: {sensor.highlights.battery_life}")
print(f" Sampling: {sensor.measurements.sampling_rate}")
print(f" Connectivity: {sensor.wireless_communication.connectivity}")
print(f" IP Rating: {sensor.environmental_characteristics.ip_rating}")
print(f" Supported assets: {len(sensor.supported_assets)} types")
# Retrieve the AI detection intelligence system
detection = client.detection_systems.get()
print(f"\nSystem: {detection.system_name}")
print(f" Overview: {detection.overview}")
# Walk the detection workflow steps
for step in detection.detection_workflow:
print(f" Step {step.step}: {step.title}")
# Inspect failure lifecycle stages
for stage in detection.failure_lifecycle.stages:
print(f" Lifecycle: {stage.stage} — {stage.description}")
# Show a few detectable failure modes
for mode in detection.detectable_failure_modes[:5]:
print(f" Detects: {mode}")
# Spectral analysis tools
for tool in detection.analysis_tools.spectral_analysis.tools:
print(f" Analysis tool: {tool.name}")
print("\nexercised: sensors.get / detection_systems.get")
Returns complete hardware specifications of the Tractian Condition Monitoring Sensor including measurements, wireless communication, physical characteristics, environmental ratings, power source, supported asset types, and certifications. One round-trip to the sensor specifications page.
No input parameters required.
{
"type": "object",
"fields": {
"overview": "string - brief description of sensor capabilities",
"highlights": "object - key specs at a glance (battery_life, operating_temperature, ingress_protection, connectivity, sampling_rate, hazardous_locations)",
"sensor_name": "string - name of the sensor product",
"sensor_type": "string - sensor category",
"measurements": "object - detailed measurement capabilities (sampling_rate, acceleration, velocity, temperature, magnetometer_rotation, sample_configuration, default_setting, sampling_frequency)",
"power_source": "object - battery information (battery_type, duration, adverse_factors)",
"cybersecurity": "object - security features (encryption, certification)",
"certifications": "array of objects - compliance certifications with name and detail",
"supported_assets": "array of strings - types of rotating assets the sensor can monitor",
"wireless_communication": "object - communication specs (frequency, protocol, connectivity, bands, internal_range, line_of_sight_range)",
"physical_characteristics": "object - physical dimensions and materials (dimensions, weight, external_material, fixation)",
"environmental_characteristics": "object - environmental ratings (ip_rating, humidity, operating_temperature, hazardous_locations)"
},
"sample": {
"data": {
"overview": "Monitor vibration, ultrasound, temperature, and RPM: automatically, over LTE and in real time.",
"highlights": {
"battery_life": "3-5 years",
"connectivity": "4G/LTE (330 ft through obstacles / 3,300 ft LoS)",
"sampling_rate": "Up to 64kHz (Detailed vibration samples.)",
"ingress_protection": "IP69K sealed",
"hazardous_locations": "Class I Div 1 (ATEX/IECEx/NFPA)",
"operating_temperature": "-40°F to 250°F"
},
"sensor_name": "Tractian Condition Monitoring Sensor",
"sensor_type": "Wireless Vibration + Ultrasound Sensor",
"measurements": {
"velocity": "Up to 100 mm/s RMS",
"temperature": "From -40°F to 250° F (-40°C to 120°C)",
"acceleration": "Up to 60 g",
"sampling_rate": "From 0 Hz to 64,000 Hz",
"default_setting": "Samples every 10 minutes",
"sampling_frequency": "500Hz (64s), 1000 Hz (32s), 2000 Hz (16s), 4000Hz (8s) , 8000Hz (4s) 16000Hz (2s), 32000Hz (1s)",
"sample_configuration": "196,608 lines (per axis)",
"magnetometer_rotation": "Up to 48,000 RPM"
},
"power_source": {
"duration": "Between 3-5 years on default settings",
"battery_type": "Lithium battery",
"adverse_factors": "Temperature, transmission distance, and data acquisition configuration"
},
"cybersecurity": {
"encryption": "Encrypted AES (256 bits)",
"certification": "FCC"
},
"certifications": [
{
"name": "FedRAMP® High",
"detail": "GovCloud; On-Prem / Edge; Air-Gapped / Disconnected"
},
{
"name": "Class I Div 1",
"detail": "ATEX/IECEx/NFPA compliant"
}
],
"supported_assets": [
"Axial Fans",
"Bearings",
"Centrifugal Compressors",
"Electric Motors",
"Gearboxes",
"Turbines"
],
"wireless_communication": {
"bands": "6 frequency channels, dynamically assigned",
"protocol": "IEEE 802.15.4g",
"frequency": "915MHz ISM",
"connectivity": "LTE/4G mobile networks, with no need to rely on industrial Wi-Fi",
"internal_range": "Up to 330ft (100m) between sensor and receiver, depending on the industrial plant topology",
"line_of_sight_range": "Up to 3,300ft (1km) between sensor and receiver, depending on the industrial plant topology"
},
"physical_characteristics": {
"weight": "180g / 6.4 oz (sensor) 22g / 0.8oz (shorter base) 50g / 1.75oz (taller base)",
"fixation": "Sensor base must be glued or screwed to the asset",
"dimensions": "40 (W) x 71 (H) x 40 (D) mm or 1.6 (W) x 2.8 (H) x 1.6 (D) in, excluding sensor base",
"external_material": "Engineered Polymer"
},
"environmental_characteristics": {
"humidity": "Suitable for installation in high humidity areas",
"ip_rating": "IP69K",
"hazardous_locations": "Complies with ATEX, NFPA 70 CL1, CL2, and CL3 (All Division I).",
"operating_temperature": "From -40°F to 250° F (-40°C to 120°C)"
}
},
"status": "success"
}
}About the Tractian API
Hardware Specifications
The get_hardware_specifications endpoint returns the complete technical profile of Tractian's condition monitoring sensor. The measurements object covers sampling rate, acceleration, velocity, temperature, magnetometer rotation, and sample configuration. The wireless_communication object details frequency, protocol, connectivity type, supported bands, internal range, and line-of-sight range. Additional fields include power_source (battery type, duration, and adverse factors), certifications (an array of compliance objects with name and detail), supported_assets (an array of rotating asset types the sensor can monitor), and cybersecurity (encryption method and certification). The highlights object surfaces a quick-reference summary of battery life, operating temperature, ingress protection rating, connectivity, and sampling rate.
Detection Intelligence
The get_detection_intelligence endpoint describes how Tractian's AI layer processes sensor data. The detectable_failure_modes array lists every fault type the system can identify. The detection_workflow array delivers ordered steps — each with a step number, title, and description — showing how a fault moves from raw signal to diagnosed issue. The data_sampling_modes array describes available sampling configurations by name and description. The failure_lifecycle object maps stages from initial fault detection through to fix verification. The ai_capabilities object covers automated diagnostics, criticality-based alarms, the Copilot AI assistant, and real-time/historical pattern recognition. The supervised_analysis object documents expert validation processes and the initial health report feature.
Response Structure
Both endpoints take no input parameters — each returns a single, fully structured object on every call. Field depth varies: some values are flat strings (sensor_name, sensor_type, system_name), while others are nested objects or arrays. Consumers who need specific sub-fields like measurements.acceleration or wireless_communication.bands will need to destructure the response on their side.
The Tractian API is a managed, monitored endpoint for tractian.com — not a raw scraper you maintain. Every endpoint is automatically health-checked on a schedule, and when tractian.com changes and a check fails, the API is automatically queued for repair and re-verified. It is built to keep working as the site underneath it changes.
This isn't an official tractian.com API — it's an independent, maintained REST wrapper over public data. Where the source has no official API (or only a limited one), Parse gives you a stable contract over a source that never promised one, and keeps it current. Need a new endpoint or field? You can revise it yourself in plain English and the agent rebuilds it against the live site in minutes — contributing the change back to the shared API is free.
Will this API break when the source site changes?+
Is this an official API from the source site?+
Can I fix or extend this API myself if I need a new endpoint or field?+
What happens if I call an endpoint that has an issue?+
- Build a product comparison tool that displays Tractian sensor specs alongside competitor hardware using fields from
measurementsandwireless_communication. - Populate a maintenance platform's knowledge base with Tractian's
detectable_failure_modesarray to map sensor alerts to known fault types. - Generate automated technical datasheets using
certifications,supported_assets, andhighlightsfrom the hardware endpoint. - Integrate Tractian's
detection_workflowsteps into an onboarding flow so field engineers understand the fault-to-resolution process. - Audit compliance coverage by extracting the
certificationsarray and cross-referencing with regulatory requirements for industrial deployments. - Display
data_sampling_modesoptions in a configuration UI so operators can select the right mode for their asset criticality level. - Feed
failure_lifecyclestage definitions into a CMMS to align Tractian alarm states with internal work order workflows.
| Tier | Price | Credits/month | Rate limit |
|---|---|---|---|
| Free | $0/mo | 200 | 5 req/min |
| Hobby | $30/mo | 1,000 | 20 req/min |
| Developer | $100/mo | 5,000 | 100 req/min |
| Team | $300/mo | 20,000 | 300 req/min |
| Company | $1,000/mo | 100,000 | 500 req/min |
Each endpoint has a fixed posted price per successful call — most fall between 1 and 10 credits — shown on this API's page before you run it. Exceeding the rate limit returns a 429 response. Authenticate with the X-API-Key header.
Does Tractian offer an official developer API?+
What does `get_detection_intelligence` return beyond failure modes?+
detectable_failure_modes array, the endpoint returns the detection_workflow as an ordered array of step objects, data_sampling_modes with name and description per mode, the failure_lifecycle object covering each stage from fault detection to fix verification, ai_capabilities describing the Copilot assistant and criticality-based alarms, analysis_tools for spectral workspace features, and supervised_analysis covering expert validation and the initial health report.Does the API cover multiple sensor models or hardware generations?+
get_hardware_specifications returns data for a single sensor product identified by sensor_name and sensor_type. Multiple models or generational comparisons are not covered. You can fork this API on Parse and revise it to add endpoints for additional Tractian sensor variants.Is real-time sensor telemetry or live equipment readings available through this API?+
Are there any fields in `get_hardware_specifications` that may be incomplete?+
highlights field description notes a truncation marker (hazardous_lo...) in the source spec, suggesting the hazardous location rating detail may be abbreviated. Consumers relying on that specific sub-field should verify completeness against the full certifications array, which provides structured name and detail pairs for each compliance listing.