Who this is for
This option is for businesses that already have a web platform or backend service and want Track Any Device to deliver real-time device updates into that system. Instead of speaking device protocols directly, your team provides the API contract and authorisation process.
What you provide
- Your REST endpoint URL and preferred method (POST, PUT, or PATCH) for receiving live updates.
- Your authorisation process — headers (e.g. API keys or bearer tokens), query parameters, tenant-auth flow, or registration requirements.
- The payload shape and field mapping your API expects.
- Any environment or rollout constraints we should handle during delivery.
What we provide
- Real-time signal forwarding from Track Any Device to your REST API.
- A configurable field map — device, tenant, and signal values (location, speed, battery, temperature, altitude, direction, recorded time) mapped to the payload keys your API expects.
- Template variables such as {device_imei} or {tenant_slug} in the endpoint URL, headers, and body parameters.
- Support for tenant onboarding when your API requires an external registration step first, plus test deliveries and delivery-health monitoring before go-live.
Typical rollout
- Share your authorisation process and REST API details with our team.
- We configure endpoint URLs, headers, params, field mapping, and onboarding rules.
- We run test deliveries and verify your API receives them.
- After sign-off, your API starts receiving real-time updates from live devices.
Need deeper integration?
By default we provide forwarding, and we are ready to customise the integration when your workflow needs more than standard delivery. Contact sales@tadpak.pk with your API details and business requirements.