Authorized APIs Sample Clauses

Authorized APIs. City shall be permitted to access and use Contractor’s SaaS Application Program Interfaces (APIs) when commercially available to develop and modify, as necessary, macros and user interfaces for use with any existing or future City systems and infrastructure. For purposes of this Agreement, such development shall be deemed an authorized modification but will not be supported by Contractor unless provided for in this Agreement. Functionality and compatibility of City developed macros will be sole responsibility of City. Any such macros or user interfaces developed by City shall become the property of City. All flat-file exchanges will be over an encrypted file transport service (ftps/vsftpd/scp/sftp) to a secure private ftp site.
AutoNDA by SimpleDocs
Authorized APIs. The City shall be permitted to access and use Contractor’s SaaS Application Program Interfaces (APIs) to develop system interfaces. For purposes of this Agreement, such development shall be deemed an authorized modification and shall become the property of City.
Authorized APIs. County shall be permitted to access and use Contractor's SaaS or On- Premise Application Program Interfaces (APIs) when commercially available to develop and modify, as necessary, macros and user interfaces for use with any existing or future County systems and infrastructure. For purposes of this Agreement, such development shall be deemed an authorized modification but will not be supported by Contractor. Functionality and compatibility of County developed macros will be sole responsibility of County. Any such macros or user interfaces developed by County shall become the property of County. All flat-file exchanges will be over an encrypted file transport service (FTPS/VSFTPD/SCP/SFTP) to a secure private ftp site.
Authorized APIs. City shall be permitted to access and use Contractor’s Application Program Interfaces (APIs) directly related to Contractor’s provision of the Services, which shall be and remain the sole property of Contractor, when commercially available to develop and modify, as necessary, macros and user interfaces for use with any existing or future City systems and infrastructure. For purposes of this Agreement, such development shall be deemed an authorized modification but will not be supported by Contractor unless provided for in this Agreement. Functionality and compatibility of City-developed macros will be sole responsibility of City. Any such macros or user interfaces developed by City shall become the property of City. All flat-file exchanges will be over an encrypted file transport service (ftps/vsftpd/scp/sftp) to a secure private ftp site.
Authorized APIs. City shall be permitted to access and use Contractor’s SaaS Application Program Interfaces (APIs) when commercially available to develop and modify, as necessary, macros, and user interfaces for use with any existing or future City systems and infrastructure. For purposes of this Term Sheet and the Agreement, such development shall be deemed an authorized modification but will not be supported by Contractor unless provided for in this Term Sheet and the Agreement. Functionality and compatibility of City developed macros will be sole responsibility of City. Any such macros or user interfaces developed by City shall become the property of City. All flat-file exchanges will be over an encrypted file transport service (ftps/vsftpd/scp/sftp) to a secure private ftp site.
Authorized APIs. County shall be permitted to access and use Contractor’s Application Program Interfaces (APIs) when commercially available to develop and modify, as necessary, macros and user interfaces for use with any existing or future County systems and infrastructure. For purposes of this Agreement, such development shall be deemed an authorized modification but will not be supported by Contractor. Functionality and compatibility of County developed macros will be sole responsibility of County. Any such macros or user interfaces developed by County shall become the property of County. All data transactions via API, whether via file transfer, REST, or other supported methods by the software solution must abide by the following security features. 1) Encryption in transport, all data transmission shall use, at minimum, TLS 1.2. 2) Encryption at rest, all data must be encrypted with a minimum of AES256. 3) Access to data must use multiple-factor authentication and/or support XXXX 2.0 4) API requests should be configured with quotas and/or throttled to prevent DdoS attacks, parameter tampering, code injections, etc. 5) All API activities shall be logged. The log events shall be accessible for review for 90 days.

Related to Authorized APIs

  • Authorized Uses The Participating Institutions and the Authorized Users may make all use of the Licensed Materials as is consistent with the applicable law and with this Agreement, including but not limited to the following licensing conditions ("Authorized Uses"). In addition, the Licensed Materials may be used for purposes of research, education or other non-commercial use as particularly follows:

Draft better contracts in just 5 minutes Get the weekly Law Insider newsletter packed with expert videos, webinars, ebooks, and more!