GPS API setup and GoDaddy cPanel

How platform administrators prepare a GPS provider connection without promising an unavailable feed.

Only authorized administrators configure tracking in API keys & settings → GPS tracking. The platform supports an existing Traccar API connection. Owners view only their assigned vehicles through GPS monitoring, without receiving fleet credentials.

SinoTrack cloud API is the chosen primary setup path for unconfigured GoDaddy accounts. Existing enabled Traccar connections are preserved. Advanced provider settings remain available for an intentional switch; the default choice does not mean a working cloud connector is already available.

The SinoTrack cloud option is setup planning, pending supplier documentation, account API access and an implemented/tested connector. It cannot be activated by entering a general website URL. The supplier must confirm endpoints, authentication, timestamps, GPS validity, speed units, rate limits, fees and exact device compatibility.

The administrator can save supplier-confirmed documentation and API-base URLs plus an optional account reference, and copy a supplier inquiry. Do not enter passwords or API tokens in these planning fields. The setup check sends no request to those URLs and reports Awaiting API documentation.

Saving a provider switch to SinoTrack cloud stops the existing Traccar feed. Traccar credentials and bindings are retained; select Traccar again to resume a configured connection. Cloud device binding and polling remain unavailable.

On GoDaddy cPanel, PHP/cURL and an allowed cron schedule can support a future HTTPS cloud connector. SSH alone does not establish permission for an always-running GPS receiver or raw inbound TCP/UDP ports. Confirm those hosting capabilities separately. Displayed map coordinates must come from actual reports with timestamps and stale/offline indicators; a map API key does not receive tracker data.