Laserfiche WebLink
<br /> <br /> <br />Consulting Services Agreement between City of San Leandro and Axon Enterprise, Inc. for Fleet 3 <br />Advanced Last revised [12/19/2023] <br /> Exhibit D – Page 14 of 1 <br /> <br /> <br />Axon Application Programming Interface Appendix <br />This Appendix applies if Axon’s API Services are included on the Quote. <br />1. Definitions. <br />1.1. "API Client" means the software that acts as the interface between City’s computer and the server, <br />which is already developed or to be developed by City. <br />1.2. "API Interface" means software implemented by City to configure City’s independent API Client <br />Software to operate in conjunction with the API Service for City’s authorized Use. <br />1.3. "Axon Evidence Partner API, API or Axon API" (collectively "API Service") means Axon’s API which <br />provides a programmatic means to access data in City’s Axon Evidence account or integrate City’s <br />Axon Evidence account with other systems. <br />1.4. "Use" means any operation on City’s data enabled by the supported API functionality. <br />2. Purpose and License. <br />2.1. City may use API Service and data made available through API Service, in connection with an API <br />Client developed by City. Axon may monitor City’s use of API Service to ensure quality, improve Axon <br />devices and services, and verify compliance with this Agreement. City agrees to not interfere with such <br />monitoring or obscure from Axon City’s use of API Service. City will not use API Service for commercial <br />use. <br />2.2. Axon grants City a non-exclusive, non-transferable, non-sublicensable, worldwide, revocable right and <br />license during the Term to use API Service, solely for City’s Use in connection with City’s API Client. <br />2.3. Axon reserves the right to set limitations on City’s use of the API Service, such as a quota on operations, <br />to ensure stability and availability of Axon’s API. Axon will use reasonable efforts to accommodate use <br />beyond the designated limits. <br />3. Configuration. City will work independently to configure City’s API Client with API Service for City’s applicable <br />Use. City will be required to provide certain information (such as identification or contact details) as part of the <br />registration. Registration information provided to Axon must be accurate. City will inform Axon promptly of any <br />updates. Upon City’s registration, Axon will provide documentation outlining API Service information. <br />4. City Responsibilities. When using API Service, City and its end users may not: <br />4.1. use API Service in any way other than as expressly permitted under this Agreement; <br />4.2. use in any way that results in, or could result in, any security breach to Axon; <br />4.3. perform an action with the intent of introducing any viruses, worms, defect, Trojan horses, malware, or <br />any items of a destructive nature to Axon Devices and Services; <br />4.4. interfere with, modify, disrupt or disable features or functionality of API Service or the servers or <br />networks providing API Service; <br />4.5. reverse engineer, decompile, disassemble, or translate or attempt to extract the source code from API <br />Service or any related software; <br />4.6. create an API Interface that functions substantially the same as API Service and offer it for use by third <br />parties; <br />4.7. provide use of API Service on a service bureau, rental or managed services basis or permit other <br />individuals or entities to create links to API Service; <br />4.8. frame or mirror API Service on any other server, or wireless or Internet-based device; <br />4.9. make available to a third-party, any token, key, password or other login credentials to API Service; <br />DocuSign Envelope ID: E1B6788D-C642-4C4D-8553-CFF844DE231E