Legal Center

API Terms of Use

Last Updated: October 7, 2026

These Developer API Terms of Service (the “API Terms” or “Agreement”) govern access to and use of the application programming interfaces, developer tools, documentation, credentials, data interfaces, and related services made available by Sonar Telematics USA, LLC (“Sonar Telematics,” “we,” “us,” or “our”).

By requesting, accessing, or using the Sonar Telematics API, creating or using API credentials, developing an Integration, or otherwise using any portion of the API, you agree to these API Terms.

If you access or use the API on behalf of a company or other legal entity, you represent that you have authority to bind that entity to this Agreement.

These API Terms supplement the applicable Sonar Telematics Terms of Service, Privacy Policy, subscription terms, Documentation, and any separate written agreement between you and Sonar Telematics. If a separate written agreement expressly governs your API use and conflicts with these API Terms, that agreement will control to the extent of the conflict.

1. Definitions

“API” means the application programming interfaces, endpoints, authentication mechanisms, specifications, and related technologies made available by Sonar Telematics.

“API Credentials” means API keys, tokens, secrets, or other credentials used to access the API.

“Developer” means the individual or entity accessing or using the API or developing, operating, or maintaining an Integration.

“End User” means an individual or entity whose authorized Sonar Telematics account, vehicles, devices, or information may be accessed through an Integration.

“Integration” means any software application, platform, system, workflow, or service that connects to or uses the API.

“Sonar Telematics Data” means information made available through the API, including, where available and authorized, vehicle location, fleet location, trips, historical events, ignition status, speed, odometer, voltage, coolant temperature, fuel information, engine RPM, diagnostic trouble codes, vehicle information, telematics information, and device status.

“Service” means Sonar Telematics' GPS tracking, telematics, fleet management, vehicle diagnostics, mobile applications, web applications, devices, APIs, software, and related services.

2. API License and Access

Subject to these API Terms and the applicable Documentation, Sonar Telematics grants Developer a limited, revocable, non-exclusive, non-transferable, and non-sublicensable right to access and use the API solely to:

1. access Sonar Telematics Data that Developer or an authorized End User is permitted to access;
2. integrate authorized Sonar Telematics functionality or data into Developer's own systems or software; and
3. make authorized Sonar Telematics Data available to End Users who have the legal right to access that data.

No rights are granted except those expressly stated in this Agreement.

Developer must maintain any Sonar Telematics account, subscription, device activation, or other authorization required for the data being accessed.

Sonar Telematics may approve, limit, suspend, or revoke API access when reasonably necessary to protect the Service, its customers, or comply with applicable law.

3. Read-Only Access

Unless Sonar Telematics expressly provides otherwise in writing or in the applicable Documentation, the Sonar Telematics API is a read-only interface.

The API may allow Developers to retrieve information from the Service but does not authorize Developers to alter vehicle information, control vehicles, modify tracker configurations, issue vehicle commands, change account settings, or otherwise write information to the Sonar Telematics platform.

The availability of an endpoint does not constitute authorization to use it outside the purposes described in the Documentation.

4. API Credentials and Security

Developer is responsible for maintaining the confidentiality and security of all API Credentials.

Developer must not:

• publicly disclose API Credentials;
• publish credentials in public repositories;
• embed secret credentials in publicly accessible source code;
• transfer or share credentials with unauthorized parties;
• use credentials issued to one customer to access another customer's data; or
• circumvent authentication or authorization controls.

Developer must promptly notify Sonar Telematics if API Credentials are lost, compromised, exposed, or used without authorization.

Sonar Telematics may revoke or rotate API Credentials where reasonably necessary for security, operational, legal, or compliance purposes.

5. Developer Responsibilities

Developer is solely responsible for its Integration and its use of the API.

Developer must:

• access only data that Developer and its End Users are authorized to access;
• use Sonar Telematics Data only for lawful and legitimate purposes;
• maintain reasonable technical and organizational safeguards;
• comply with applicable privacy, data protection, employment, surveillance, consumer protection, transportation, and other laws;
• avoid exposing Sonar Telematics Data to unauthorized persons; and
• avoid interfering with the operation, security, or availability of the API or Service.

Developer is responsible for activity performed through its systems or API Credentials.

6. End Users, Drivers, and Consent

Telematics data may relate to vehicle owners, operators, employees, contractors, renters, customers, family members, or other individuals.

Developer is solely responsible for determining whether notice, consent, authorization, acknowledgment, agreement, or another lawful basis is required before collecting, accessing, using, storing, sharing, or displaying Sonar Telematics Data.

Developer represents and warrants that it has obtained and will maintain all rights, permissions, notices, and consents required by applicable law.

Developer may not use the API to unlawfully track, monitor, profile, discriminate against, harass, stalk, or surveil any person.

Sonar Telematics' technical ability to make information available through the API does not mean that Developer's intended use of that information is lawful.

7. Permitted Uses

Subject to applicable law and these API Terms, Sonar Telematics Data may be used for legitimate purposes such as:

• fleet and vehicle monitoring;
• trip and mileage analysis;
• operational reporting;
• vehicle utilization analysis;
• driver or fleet management;
• vehicle diagnostics and maintenance analysis;
• internal business analytics;
• rental fleet management;
• customer-owned software integrations;
• dispatch and operational workflows; and
• other authorized telematics-related functionality.

8. Prohibited Uses

Developer may not, directly or indirectly:

1. access the API or Sonar Telematics Data without authorization;
2. access data belonging to another customer, account, vehicle, or End User without authorization;
3. sell, rent, sublicense, distribute, or otherwise make the API itself available to third parties;
4. resell API access unless expressly authorized by Sonar Telematics;
5. circumvent rate limits, authentication, usage restrictions, or security controls;
6. scrape the Service or use undocumented methods to obtain data intended to be accessed through the API;
7. reverse engineer, decompile, disassemble, modify, or attempt to discover non-public aspects of the API or Service, except where such restriction is prohibited by law;
8. interfere with, overload, damage, disable, or disrupt the API or Service;
9. introduce malicious code or attempt unauthorized access to Sonar Telematics systems;
10. use Sonar Telematics Data for unlawful surveillance, stalking, harassment, profiling, or discrimination;
11. use the API or Sonar Telematics Data in violation of applicable law;
12. falsely state or imply that Sonar Telematics sponsors, certifies, endorses, or guarantees an Integration; or
13. use the API in a manner that creates a material legal, security, operational, privacy, or reputational risk to Sonar Telematics or its customers.

9. Rate Limits and Technical Requirements

Sonar Telematics may establish technical limits relating to request frequency, concurrent requests, historical data access, polling frequency, authentication, data volume, or other resource usage.

Developer must comply with those limits.

Sonar Telematics may throttle, reject, delay, or temporarily restrict requests that exceed applicable limits or could negatively affect the Service.

Developer is responsible for the development, hosting, maintenance, security, testing, and operation of its Integration unless otherwise agreed in writing.

10. API Changes and Availability

Sonar Telematics may add, remove, modify, replace, deprecate, or discontinue API endpoints, fields, response formats, authentication mechanisms, Documentation, or functionality.

Where commercially reasonable, Sonar Telematics may provide advance notice of material changes that are expected to require substantial modifications to existing Integrations.

Sonar Telematics may make changes without advance notice where reasonably necessary for security, legal compliance, fraud prevention, system stability, emergency maintenance, or protection of the Service.

Developer is responsible for keeping its Integration compatible with the API.

11. Accuracy and Limitations of Telematics Data

Vehicle telematics systems depend on technologies and conditions that may be outside Sonar Telematics' direct control.

Data availability, accuracy, frequency, or timing may be affected by factors such as:

• cellular network availability;
• GPS or satellite reception;
• tunnels, garages, buildings, or underground locations;
• device installation or removal;
• vehicle power;
• vehicle manufacturer protocols;
• CAN bus or OBD-II availability;
• vehicle configuration;
• third-party telecommunications providers;
• firmware;
• server connectivity;
• maintenance;
• interference; or
• environmental conditions.

Location, speed, fuel, diagnostic, odometer, engine, posted-speed, event, and other telematics information may contain delays, inaccuracies, gaps, estimates, or errors.

The API and Sonar Telematics Data should not be relied upon as the sole method for emergency response, life-safety functions, accident prevention, law enforcement activities, or other applications where inaccurate, delayed, or unavailable data could reasonably result in death, personal injury, or significant property damage.

12. Privacy, Data Protection, and Security

Sonar Telematics' collection and processing of personal information is governed by the applicable Sonar Telematics Privacy Policy.

Developer is independently responsible for its own privacy practices and must maintain any notices, policies, consents, and safeguards required by law.

Developer must maintain reasonable administrative, technical, organizational, and physical safeguards appropriate to the nature of Sonar Telematics Data accessed through the API.

Developer must take reasonable measures to protect data in transit and at rest, restrict access to authorized persons, protect API Credentials, maintain appropriate authentication controls, remediate known security vulnerabilities, and securely delete data when it is no longer needed or authorized to be retained.

Developer must promptly notify Sonar Telematics of a security incident that materially affects Sonar Telematics Data, API Credentials, the API, or the Service.

13. Intellectual Property and Branding

Sonar Telematics and its licensors retain all right, title, and interest in and to the Service, API, Documentation, platform, software, technology, databases, interfaces, systems, trademarks, logos, and related intellectual property.

Developer retains ownership of its independently developed Integration, excluding Sonar Telematics technology, materials, or intellectual property incorporated into or accessed through the Integration.

These API Terms do not grant Developer a general right to use Sonar Telematics trademarks or branding.

Developer may factually state that its product “integrates with Sonar Telematics” or uses the “Sonar Telematics API,” provided the statement is accurate and does not imply sponsorship, certification, partnership, or endorsement.

14. Third-Party Services

The Service may depend upon or interoperate with third-party products, networks, mapping services, telecommunications providers, hosting providers, vehicle systems, or other services.

Sonar Telematics does not control all third-party services and does not guarantee their continuous availability.

Sonar Telematics is not responsible for failures attributable to third-party services outside its reasonable control.

15. Suspension and Termination

Sonar Telematics may limit or suspend API access where it reasonably determines that:

• Developer has violated these API Terms;
• API Credentials have been compromised;
• Developer's Integration creates a security vulnerability;
• API use threatens the stability or availability of the Service;
• unauthorized access to Sonar Telematics Data may have occurred;
• suspension is required by law; or
• Developer's use creates a material risk to Sonar Telematics, its customers, or third parties.

Sonar Telematics may terminate Developer's API access upon reasonable notice or immediately in cases involving material breach, unlawful activity, unauthorized data access, circumvention of technical safeguards, or material security or privacy risk.

Upon termination, Developer must stop using the API and API Credentials and must delete Sonar Telematics Data where required by law, contractual obligations, End User instructions, or applicable Documentation.

16. Disclaimer of Warranties

TO THE MAXIMUM EXTENT PERMITTED BY APPLICABLE LAW, THE API, SERVICE, DOCUMENTATION, AND SONAR TELEMATICS DATA ARE PROVIDED “AS IS” AND “AS AVAILABLE.”

SONAR TELEMATICS DISCLAIMS ALL WARRANTIES, EXPRESS, IMPLIED, STATUTORY, OR OTHERWISE, INCLUDING WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, TITLE, NON-INFRINGEMENT, ACCURACY, RELIABILITY, OR AVAILABILITY.

SONAR TELEMATICS DOES NOT WARRANT THAT:

1. THE API OR SERVICE WILL BE AVAILABLE AT ALL TIMES;
2. THE API WILL OPERATE WITHOUT INTERRUPTION OR ERROR;
3. SONAR TELEMATICS DATA WILL ALWAYS BE COMPLETE, CURRENT, ACCURATE, OR DELIVERED IN REAL TIME;
4. GPS, CELLULAR, VEHICLE, ENGINE, FUEL, DIAGNOSTIC, POSTED-SPEED, ODOMETER, OR OTHER DATA WILL ALWAYS BE AVAILABLE OR ACCURATE; OR
5. AN INTEGRATION WILL REMAIN COMPATIBLE WITH FUTURE VERSIONS OF THE API.

17. Indemnification

To the fullest extent permitted by law, Developer agrees to defend, indemnify, and hold harmless Sonar Telematics USA, LLC, its affiliates, officers, directors, employees, agents, contractors, licensors, and service providers from and against third-party claims, damages, losses, liabilities, penalties, costs, and reasonable attorneys' fees arising out of or relating to:

1. Developer's Integration;
2. Developer's or an End User's use or misuse of the API;
3. Developer's use, disclosure, or processing of Sonar Telematics Data;
4. Developer's violation of these API Terms or applicable law;
5. Developer's failure to obtain legally required notices, permissions, or consents;
6. unauthorized access resulting from Developer's systems or credentials; or
7. allegations that Developer's Integration infringes or violates third-party rights.

18. Limitation of Liability

TO THE MAXIMUM EXTENT PERMITTED BY APPLICABLE LAW, SONAR TELEMATICS AND ITS AFFILIATES, OFFICERS, DIRECTORS, EMPLOYEES, AGENTS, CONTRACTORS, LICENSORS, AND SERVICE PROVIDERS WILL NOT BE LIABLE FOR ANY INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, PUNITIVE, OR CONSEQUENTIAL DAMAGES, INCLUDING LOSS OF PROFITS, REVENUE, BUSINESS, GOODWILL, DATA, OR USE, ARISING OUT OF OR RELATING TO THE API, SERVICE, SONAR TELEMATICS DATA, DOCUMENTATION, OR THIS AGREEMENT.

TO THE MAXIMUM EXTENT PERMITTED BY LAW, SONAR TELEMATICS' TOTAL AGGREGATE LIABILITY ARISING OUT OF OR RELATING TO THESE API TERMS OR DEVELOPER'S USE OF THE API WILL NOT EXCEED THE GREATER OF:

• THE AMOUNT ACTUALLY PAID BY DEVELOPER TO SONAR TELEMATICS FOR THE APPLICABLE SERVICE DURING THE TWELVE (12) MONTHS IMMEDIATELY PRECEDING THE EVENT GIVING RISE TO THE CLAIM; OR
• ONE HUNDRED U.S. DOLLARS ($100).

19. General Terms

Developer and Sonar Telematics are independent parties. Nothing in these API Terms creates an employment, agency, partnership, franchise, fiduciary, joint venture, or similar relationship.

Developer may not assign or transfer these API Terms or its API rights without Sonar Telematics' prior written consent. Sonar Telematics may assign these API Terms in connection with a merger, acquisition, corporate reorganization, sale of assets, change of control, or by operation of law.

Sonar Telematics will not be liable for delays or failures caused by circumstances beyond its reasonable control, including natural disasters, severe weather, war, civil unrest, governmental action, telecommunications failures, cellular network outages, Internet failures, hosting provider failures, or utility failures.

Sonar Telematics may update these API Terms from time to time. When changes are material, Sonar Telematics may provide notice through the Service, by email, through the Documentation, or by another reasonable method.

Failure by Sonar Telematics to enforce any provision is not a waiver of its right to enforce that provision later.

If any provision is held unenforceable, the remaining provisions will remain in effect.

These API Terms, together with the applicable Sonar Telematics Terms of Service, Privacy Policy, Documentation, and any applicable written agreement, constitute the agreement between Developer and Sonar Telematics concerning API use.

20. Governing Law, Notices, and Contact

These API Terms and any dispute arising out of or relating to them will be governed by the laws of the State of Florida, without regard to conflict-of-law principles.

Unless otherwise required by applicable law or agreed in writing, any legal proceeding arising out of or relating to these API Terms will be brought in a state or federal court of competent jurisdiction located in Florida.

Legal notices and questions regarding the Sonar Telematics API or these API Terms may be directed to:

Sonar Telematics USA, LLC

Attn: Legal

1073 Willa Springs Drive, Suite 2021
Winter Springs, FL 32708
United States

Email: notifications@sonartelematics.com