Home / Solutions
TruCount Pro JSON Sensor Ingest API
TruCount Pro accepts authenticated JSON sensor submissions and uses payload mapping to associate incoming fields with readings the platform can display and monitor. This allows integrations to send measurements from buildings, industrial facilities and remote assets into the same console. The API is part of the platform's sensor onboarding and reporting workflow.
Start by identifying the device and the readings it should supply. A payload may represent temperature, level, occupancy or another supported measurement. Identify the JSON fields that carry the readings and confirm their meaning and units before mapping them. Give the sensor a name and associate it with the site or group where operators will find it.
How it works
Once the integration is authenticated and the mapping is in place, send a sample from the integration environment. Check the resulting reading in the console and confirm that it appears under the intended sensor. Review the value, unit and time. If they differ from what the integration sent, check the mapping before using that reading in an operational alert.
Set up the dashboard around the people who will use it. The operator checking conditions needs to find the relevant site, group and sensor quickly. The person responding to an incident also needs the time and reading that caused the alert. Agree on clear names and use the same names in rules so those two views make sense together.
Example alert rule
Map a temperature reading for a cold store and verify that it appears as temperature in the console. Configure a high rule for that measurement and require a sustained breach before alerting. If the condition persists, the duty contact receives an email and can inspect the reading history and assign someone to investigate.
Review readings and coordinate a response
Decide who should receive an email and who will take ownership when an incident opens. Acknowledge it to show that someone is responding, then assign it if another person needs to investigate. During planned work, use a maintenance or suppression window where appropriate. After the work, check that the expected readings are arriving again.
When reviewing an incident, use a time window that includes readings before the alert and after the condition cleared. Keep the measurement and unit consistent so the comparison is meaningful. A CSV export lets a colleague inspect the same readings, while the incident record keeps the response and assignment visible to the team.
Frequently asked questions
Does ingest require authentication?
Yes. Use the integration's authorised credentials. Keep them out of public documentation, shared examples and screenshots.
What is payload mapping for?
Mapping associates incoming JSON fields with the sensor readings TruCount Pro uses for display, historical review and alerting.
How can I check that a mapping works?
Send a sample through the authenticated integration and check the displayed sensor, measurement, unit and timestamp in the console.
Can mapped readings be used for alerts?
Yes. Verify the mapped reading first, then select the corresponding measurement when configuring an alert rule.
Discuss your monitoring project
Tell us what you need to monitor, where the sensors are located and who should respond when conditions change.
Contact TruCount Pro →Related guides · Cold Storage Temperature Monitoring · CO2, Temperature and Humidity Monitoring