REST API overview

The TAMsys public API is a read-only JSON interface for customer device inventories and their latest telemetry readings.

Base URLs

Environment	Base URL
Primary	https://api.tamsys.app/p/
Legacy alias	https://api.tamsys.tessol.in/p/

Both hostnames expose the same production API. All paths in this documentation are relative to the /p/ base path.

Authentication

Every request requires your API key in the X-API-KEY header:

GET /p/devices/list HTTP/1.1
Host: api.tamsys.app
X-API-KEY: your-api-key
Accept: application/json

curl 'https://api.tamsys.app/p/devices/list' \
  --header 'X-API-KEY: your-api-key'

Ask TAMsys support to provision or rotate an API key for your company.

Protect API keys

Do not embed API keys in browser bundles, mobile binaries, public repositories, or logs. Call the TAMsys API from a trusted backend and load the key from a secret manager or protected environment variable.

Available endpoints

Method	Path	Returns
GET	/devices/list	Device metadata for the authenticated company
GET	/devices/data	Latest telemetry for every assigned device with data
GET	/devices/{id}/data	Latest telemetry for one assigned device
GET	/devices/multiple/data?ids={id1},{id2}	Latest telemetry for up to 100 selected devices

Continue to device endpoints for complete request and response examples.

Response conventions

• Successful responses use application/json.
• List endpoints return JSON arrays.
• The single-device endpoint returns a JSON object.
• Timestamps are Unix epoch values in milliseconds unless a device-specific field states otherwise.
• Telemetry fields vary by device model and firmware. Use id as the stable device identifier and tolerate additional fields.
• Cross-origin requests are allowed, but exposing a secret API key in client-side code is not recommended.