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.
View SourceView Similar (13)
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
View SourceView Similar (2)
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.
View Source
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.
View Source
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.
View Source
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 ▇▇▇▇ 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.
View Source

Related to Authorized APIs

  • Authorized Access Transfer Agent shall have controls that are designed to maintain the logical separation such that access to systems hosting Fund Data and/or being used to provide services to Fund will uniquely identify each individual requiring access, grant access only to authorized personnel based on the principle of least privileges, and prevent unauthorized access to Fund Data.

  • AUTHORIZED AGENTS On the Closing Date and from time to time thereafter, the Borrower shall deliver to the Administrative Agent an Officer’s Certificate setting forth the names of the employees and agents authorized to request Loans and Letters of Credit and to request a conversion/continuation of any Loan and containing a specimen signature of each such employee or agent. The employees and agents so authorized shall also be authorized to act for the Borrower in respect of all other matters relating to the Loan Documents. The Administrative Agent, the Arrangers, the Co-Agents, the Lenders and any Issuing Bank shall be entitled to rely conclusively on such employee’s or agent’s authority to request such Loan or Letter of Credit or such conversion/continuation until the Administrative Agent and the Arrangers receive written notice to the contrary. None of the Administrative Agent or the Arrangers shall have any duty to verify the authenticity of the signature appearing on any written Notice of Borrowing or Notice of Conversion/Continuation or any other document, and, with respect to an oral request for such a Loan or Letter of Credit or such conversion/continuation, the Administrative Agent and the Arrangers shall have no duty to verify the identity of any person representing himself or herself as one of the employees or agents authorized to make such request or otherwise to act on behalf of the Borrower. None of the Administrative Agent, the Arrangers or the Lenders shall incur any liability to the Borrower or any other Person in acting upon any telephonic or facsimile notice referred to above which the Administrative Agent or the Arrangers believes to have been given by a person duly authorized to act on behalf of the Borrower and the Borrower hereby indemnifies and holds harmless the Administrative Agent, each Arranger and each other Lender from any loss or expense the Administrative Agent, the Arrangers or the Lenders might incur in acting in good faith as provided in this Section 2.7.

  • Authorized Agent Authorized Agent means the individual(s) appointed in writing by the Depositor (or by the beneficiary following the Depositor's death) authorized to perform the duties and responsibilities set forth in the Agreement on behalf of the Depositor. Code. Code means the Internal Revenue Code.

  • Authorized Affiliates The parties agree that, by executing the DPA, the Customer enters into the DPA on behalf of itself and, as applicable, in the name and on behalf of its Authorized Affiliate(s), thereby establishing a separate DPA between Okta and each such Authorized Affiliate, subject to the provisions of the Agreement. Each Authorized Affiliate agrees to be bound by the obligations under this DPA and, to the extent applicable, the Agreement. An Authorized Affiliate is not and does not become a party to the Agreement, and is only a party to the DPA. All access to and use of the Service by Authorized Affiliate(s) must comply with the terms and conditions of the Agreement and any violation thereof by an Authorized Affiliate shall be deemed a violation by Customer.

  • Authorized Contacts LightEdge Solutions provides reliable and secure managed services by requiring technical support and information requests come only from documented, authorized client-organization contacts. Additionally, in compliance with federally regulated CPNI (Customer Proprietary Network Information) rules, a customer contacting LightEdge Solutions to request an add, move, or change and/or to request information on their account, must provide LightEdge representative with customer’s Code Word. Code Word is not required or verified to open trouble tickets related to service issues, however, any subsequent information/updates or authorization of intrusive testing related to the trouble ticket will require the Code Word. Customer shall provide a “contact list” which will contain one (“1”) Administrative contact and may contain up to three (“3”) Technical contacts per service. Administrative and Technical contacts are authorized to request service changes or information, including the contact name, contact e-mail address and contact phone number for each contact but must provide customer Code Word for any CPNI related requests. Requests to change a contact on the list or to change the Code Word must be submitted by the Administrative contact. Requests to replace the Administrative contact shall be submitted via fax to LightEdge on customer company letterhead. All requests are verified per procedure below.  Requests for CPNI, configuration information or changes are accepted only from documented, authorized client-organization contacts via e-mail, fax or phone and will require Customer’s Code Word. E-mail and fax requests must be submitted without the Code Word. Customer contact will be called to verify Code Word. E- mail requests that include the Code Word will be denied and the client Administrative Contact will be notified and required to change the Code Word.  E-mail and fax requests are verified with a phone call to the documented client contact. Phone call requests must be validated with an e-mail request from a documented client contact.