API Keys Sample Clauses

The API Keys clause governs the issuance, use, and management of unique identifiers that allow access to an application's programming interface (API). Typically, this clause outlines how API keys are provided to users, the responsibilities for keeping them secure, and the conditions under which they may be revoked or suspended. For example, it may specify that users must not share their keys or use them for unauthorized purposes. The core function of this clause is to control and secure access to the API, thereby protecting the system from misuse and ensuring only authorized parties can interact with the service.
POPULAR SAMPLE Copied 7 times
API Keys. In order to access the Widget Application, Processor may require Merchant to register for a unique security key or other security mechanism that will allow Processor to identify and manage Merchant’s connection to the Processor platform. Processor may then issue Merchant one or more unique security keys, tokens, passwords and/or other credentials (collectively, “Keys”) for accessing the Widget Application. Merchant may only access the Widget Application with the Keys issued by Processor. Merchant may not sell, transfer, sublicense or otherwise disclose Keys to any third party or use such Keys with any third-party product or service; provided, however, Merchant may allow its third party developers to use such Keys to the extent necessary to integrate the Widget Application with Merchant’s website, provided however, that Merchant will be responsible for the performance of any third party developer in the same manner as its own performance. Merchant shall be responsible for all activities that occur using its Keys by requesting API keys for testing, production and completing API certification, regardless of whether such activities are undertaken by Merchant or a third party and will notify Processor of any unauthorized use of the Keys.
View SourceView Similar (2)
API Keys. In order to use the HelloSign APIs, Customer must obtain its unique API credentials an ("API Key") via the registration process. Customer is solely responsible for all activity associated with its API Key, regardless of whether it has knowledge of such activity. Customer must not share its API Key with any third party, shall keep such API Key secure, and shall use it as Customer’s sole means of accessing the HelloSign API.
View SourceView Similar (3)
API Keys. SynapseFI will provide you with separate API Keys for your Platform Account to interact with the API and UAT environment. Prior to receiving production API Keys, you must submit your Application and related services to a review by SynapseFI. Your API Keys are Confidential Information (as defined in Section 8 ("Confidentiality")) of SynapseFI. You are prohibited from selling, transferring, sublicensing, or disclosing your API Keys or other SynapseFI credentials to any third party, other than a service provider performing services on your behalf that has been both disclosed to us in writing and approved by us in writing. You understand and agree that you are liable for any actions performed using your API Keys, Platform Account credentials or other SynapseFI credentials. Any access or attempt to access an API must comply with the integration requirements, specifications, and guidelines set out in the API Documentation, as may be updated by SynapseFI from time to time. You will not misrepresent your identity or your Application’s identity when using the APIs. SynapseFI may temporarily suspend or revoke your API Keys at any time for breach of this Agreement, breach of the Incorporated Agreements or if SynapseFI believes in our sole discretion that your access to API Keys has been compromised or your use of the Services or Bank services is otherwise a misuse or threat to SynapseFI or Bank.
View Source
API Keys you and your subcontractors, as the case may be, will be issued one or more unique security keys, tokens, passwords and/or other credentials for accessing the API (collectively ‘keys’).
View Source
API Keys. In order to access the API Services, Active may require Client to register for a unique security key or other security mechanism. Any information provided by Client in connection with such registration must be accurate, current and complete. Active may then issue Client one or more unique security keys, tokens, passwords and/or other credentials (collectively, “Access Codes”) for accessing the API Services. Client may only access the API Services with the Access Codes issued by Active. Client may not sell, transfer, sublicense or otherwise disclose Access Codes to any third party or use such Access Codes with any third-party product or service except to affect an integration otherwise allowed by this Product Attachment or Agreement. Client is responsible for maintaining the secrecy and security of the Access Codes and for all activities that occur using its Access Codes, regardless of whether such activities are undertaken by Client or a third party and will notify Active of any unauthorized use of the Access Codes.
View Source
API Keys. Dinari will provide Licensee with API Keys that permit Licensee to access the Dinari API. Any API Key is the property of Dinari and may be revoked (i) if Licensee shares them other than as allowed under this Agreement, or (ii) if any API Key is compromised, or (iii) if Licensee violates any term of this Agreement, or (iv) if either party terminates this Agreement. Licensee agrees to promptly inform ▇▇▇▇▇▇ of any changes to the usage of its API Key, including but not limited to when a Licensee User should have their API Key disabled (e.g., due to termination of such user’s employment or business relationship with Licensee).
View Source
API Keys. In order to use the Clustdoc APIs, the Customer must obtain its unique API credentials (an “API Key”) via the registration process. The customer is solely responsible for all activity associated with its API Key, regardless of whether it has knowledge of such activity. Customer must not share its API Key with any third party, shall keep such API Key secure, and shall use it as Customer’s sole means of accessing the Clustdoc API.
View Source
API Keys. To access the Services, Partner shall use its API key(s) in accordance with the Documentation.
View Source
API Keys. Licensee’s implementation and use of the SnapDiff REST APIs v3 as permitted under the terms of this Agreement may require the use of one or more unique authentication keys (each an “API Key”). If such API Key(s) are required, NetApp will issue such API Keys to Licensee, which must be referenced in all of Licensee Applications’ calls to the SnapDiff REST APIs v3. Such API Keys are NetApp Confidential Information (as defined below), may not be shared, and may not under any circumstances be used by any software that is not a Licensee Application.
View Source

Related to API Keys

  • API If the Software offers integration capabilities via an API, your use of the API may be subject to additional costs or Sage specific policies and terms and conditions (which shall prevail in relation to your use of the API). You may not access or use the API in any way that could cause damage to us or the Software, or in contravention of any applicable laws. We reserve the right in our sole discretion, to: (i) update any API from time to time; (ii) place limitations around your use of any API; and (iii) deny you access to any API in the event of misuse by you or to otherwise protect our legitimate interests.

  • Product Specifications (a) Supplier shall manufacture all Products according to the Specifications in effect as of the date of this Agreement, with such changes or additions to the Specifications of the Products related thereto as shall be requested by Buyer in accordance with this Section or as otherwise agreed in writing by the Parties. All other Products shall be manufactured with such Specifications as the Parties shall agree in writing. (b) Buyer may request changed or additional Specifications for any Product by delivering written notice thereof to Supplier not less than one hundred twenty (120) days in advance of the first Firm Order for such Product to be supplied with such changed or additional Specifications. Notwithstanding the foregoing, if additional advance time would reasonably be required in order to implement the manufacturing processes for production of a Product with any changed or additional Specifications, and to commence manufacture and delivery thereof, Supplier shall so notify Buyer, and Supplier shall not be required to commence delivery of such Product until the passage of such additional time. (c) Supplier shall be required to accommodate any change of, or additions to, the Specifications for any Product, if and only if (i) in Supplier’s good faith judgment, such changed or additional Specifications would not require Supplier to violate good manufacturing practice, (ii) the representation and warranty of Buyer deemed made pursuant to Subsection (e) below is true and correct, and (iii) Buyer agrees to reimburse Supplier for the incremental costs and expenses incurred by Supplier in accommodating the changed or additional Specifications, including the costs of acquiring any new machinery and tooling. For the avoidance of doubt, such costs and expenses shall be payable by Buyer separately from the cost of Products at such time or times as Supplier shall request. (d) Supplier shall notify Buyer in writing within thirty (30) days of its receipt of any request for changed or additional Specifications (i) whether Supplier will honor such changed or additional Specifications, (ii) if Supplier declines to honor such changed or additional Specifications, the basis therefor and (iii) if applicable, the estimated costs and expenses that Buyer will be required to reimburse Supplier in respect of the requested changes or additions, as provided in Subsection (c) above. Buyer shall notify Supplier in writing within fifteen (15) days after receiving notice of any required reimbursement whether Buyer agrees to assume such reimbursement obligation. (e) By its request for any changed or additional Specifications for any Product, Buyer shall be deemed to represent and warrant to Supplier that the manufacture and sale of the Product incorporating Buyer’s changed or additional Specifications, as a result of such incorporation, will not and could not reasonably be expected to (i) violate or conflict with any contract, agreement, arrangement or understanding to which Buyer and/or any of its Affiliates is a party, including this Agreement and any other contract, agreement, arrangement or understanding with Supplier and/or its Affiliates, (ii) infringe on any trademark, service ▇▇▇▇, copyright, patent, trade secret or other intellectual property rights of any Person, or (iii) violate any Applicable Law. Buyer shall indemnify and hold Supplier and its Affiliates harmless (including with respect to reasonable attorneys’ fees and disbursements) from any breach of this representation and warranty.

  • Samples The Contractor shall submit the following samples of Materials and relevant information to the Authority’s Engineer for pre-construction review: (a) manufacturer's test reports and standard samples of manufactured Materials; and (b) samples of such other Materials as the Authority’s Engineer may require.

  • Consumables During the design phase, Purchaser may participate in the selection of suppliers of consumables of the Supplier. In such case, the choice regarding the final selection of the said suppliers shall be mutually agreed between the Parties. Two suppliers shall be identified and selected for each type of consumables.

  • Labelling A label shall be permanently affixed on each container with at least the following information: name of the manufacturer, serial number, date of manufacture, MFP, NWP, type of fuel (e.g. "