How do you integrate a tracking API with a TMS? | A: TMS-tracking API integration follows three steps: (1) Trip creation sync — when a trip is created in the TMS, the tracking API is notified with vehicle, origin, destination, and expected delivery window; (2) Location streaming — the API returns live location updates via webhook or polling, which the TMS displays on its map; (3) Event callbacks — departure, geofence entry, halt alerts, and delivery confirmation are pushed back to the TMS as status updates. | Q: What integration method is better — webhooks or polling for tracking data? | A: Webhooks are better for real-time events (departure, halt alerts, delivery confirmation) — they push data to your TMS immediately when an event occurs, with zero latency. Polling is simpler to implement and better for periodic location updates where exact timing isn't critical. Best practice: use webhooks for event notifications and polling every 5 minutes for location breadcrumbs. | Q: What does a tracking API webhook payload look like? | A: A typical webhook payload contains: trip_id (your reference), vehicle_registration, event_type (departed / halted / arrived / delivered), timestamp, latitude, longitude, and metadata (halt duration, geofence name, deviation flag). Intugine's webhooks also include derived fields like halt_type and eta_updated to minimise the need for additional API calls. | Q: How long does a TMS-tracking API integration typically take? | A: A basic integration (trip creation + location polling + delivery confirmation) takes 1–2 weeks for a developer with REST API experience. Full integration including ERP event callbacks, exception handling, and UI embedding takes 3–6 weeks. Intugine provides a sandbox environment, Postman collections, and dedicated integration support to compress this timeline. | Q: What are the common mistakes when integrating a tracking API with a TMS? | A: The three most common mistakes are: (1) Not handling webhook retries — your TMS endpoint must acknowledge webhooks within 5 seconds or the API will retry and create duplicates; (2) Polling too frequently — polling every 30 seconds at high vehicle count burns rate limits fast; use webhooks for events and 5-minute polling for location; (3) Not testing with inactive vehicles — your TMS must handle gaps in location data gracefully. | Q: Does Intugine support SAP and Oracle TMS integration out of the box? | A: Intugine has pre-built connectors for SAP Transportation Management (TM) and SAP Extended Warehouse Management (EWM) that reduce integration time to 1–2 days. For Oracle TMS, integration uses the standard REST API with certified adapters. For custom or legacy TMS, Intugine's engineering team provides integration support and can build custom connectors on request. +
