API Prohibitions Sample Clauses

API Prohibitions. When using the APIs, you may not (or allow those acting on your behalf to) violate the HUAWEI Developers Service Agreement, and you may not: a. sublicense an API for use by any third party. Consequently, you may not create an API Client that functions substantially the same as the APIs and offer it for use by third parties. b. perform an action with the intent of introducing to Huawei products and services any viruses, worms, defects, Trojan horses, malware, or any items of a destructive nature. c. reverse engineer or attempt to extract the source code from any API or any related software, except to the extent that this restriction is expressly prohibited by applicable laws. d. use the APIs for any activities where the use or failure of the APIs could lead to death, personal injury, or environmental damage (such as the operation of air traffic control, or life support systems). e. remove, obscure, or alter any terms of the APIs Agreements or any links to or notices of those terms.
View SourceView Similar (4)
API Prohibitions. When using the APIs, you may not (or allow those acting on your behalf to):
View SourceView Similar (2)
API Prohibitions. When using the API’s, you may not (nor may those acting on your behalf): 1. Sublicense an API for use by a third party. Consequently, you will not create an API Client that functions substantially the same as the API’s and offer it for use by third parties. 2. Perform an action with the intent of damaging, gaining unauthorized access to, or stealing Trinity Cyber source code or systems 3. Interfere with or disrupt the API’s or the servers or networks providing the API’s. 4. Reverse engineer or attempt to extract the source code from any API or any related software, except to the extent that this restriction is expressly prohibited by applicable law. 5. Use the API’s for any activities where the use or failure of the API’s could lead to death, personal injury, or environmental damage (such as the operation of nuclear facilities, air traffic control, or life support systems). 6. Use the API’s to process or store any data that is subject to the International Traffic in Arms Regulations maintained by the U.S. Department of State. 7. Remove, obscure, or alter any Trinity Cyber terms of service or any links to or notices of those terms. Unless otherwise specified in writing by Trinity Cyber, Trinity Cyber does not intend use of the API’s to create obligations under the Health Insurance Portability and Accountability Act, as amended ("HIPAA"), and makes no representations that the API’s satisfy HIPAA requirements. If you are (or become) a "covered entity" or "business associate" as defined in HIPAA, you will not use the API’s for any purpose or in any manner involving transmitting protected health information to Trinity Cyber unless you have received prior written consent to such use from Trinity Cyber.
View Source
API Prohibitions. When using the APIs, you shall not (or allow those acting on your behalf to): (1) Sublicense an API for use by a third party. Consequently, you will not create an API Client that functions substantially the same as the APIs and offer it for use by third parties; (2) Interfere with or disrupt the APIs or the servers or networks providing the APIs; (3) Perform an action with the intent of introducing to PingPong products and services any viruses, worms, defects, Trojan horses, malware, or any items of a destructive nature; (4) Remove, obscure, or alter any PingPong terms of service or any links to or notices of those terms; or (5) Reverse engineer or attempt to extract the source code from any API or any related software, except to the extent that this restriction is expressly prohibited by applicable law.
View Source
API Prohibitions. When using the ▇▇▇▇▇▇ API, Customer, Business User and Candidate may not (or allow those acting on Customer behalf to): a. Copy, translate, modify, create a derivative work of, sell, lease, lend, convey, distribute, publicly display, or sublicense to any third party, the ▇▇▇▇▇▇ API, without permission of ▇▇▇▇▇▇. b. Perform an action with the intent of introducing to the ▇▇▇▇▇▇ API any viruses, worms, defects, trojan horses, malware, or any items of a destructive nature. c. ▇▇▇▇▇▇, stalk, harass, abuse, or threaten others. d. Interfere with or disrupt the ▇▇▇▇▇▇ API or the servers or networks providing the ▇▇▇▇▇▇ API. e. Promote and/or facilitate unlawful online gambling or illegal commercial messages or advertisements. f. Reverse engineer or attempt to extract the source code from the ▇▇▇▇▇▇ API or any related software. g. Use the ▇▇▇▇▇▇ API for any activities where the use or failure of the ▇▇▇▇▇▇ API could lead to death, personal injury, or environmental damage (such as the operation of nuclear facilities, air traffic control, or life support systems). h. Scrape, build databases, or otherwise create permanent copies of API Content, or keep cached copies longer than permitted by the cache header; i. Misrepresent the source or ownership; or j. Remove, obscure, or alter any copyright, trademark, or other proprietary rights notices; or falsify or delete any author attributions, legal notices, or other labels of the origin or source of material.
View Source
API Prohibitions. When using our APIs, you may not (or allow those acting on your behalf to): 1. Sublicense our APIs for use by a third party. Consequently, you will not create an API Client that functions substantially the same as any of our APIs and offer it for use by third parties without Realogy’s express prior written consent. 2. Perform an action with the intent of introducing to Realogy products and services any viruses, worms, defects, Trojan horses, malware, or any items of a destructive nature. 3. Defame, abuse, harass, stalk, or threaten others. 4. Interfere with or disrupt the APIs or the servers or networks providing the APIs. 5. Promote or facilitate unlawful online gambling or disruptive commercial messages or advertisements. 6. Reverse engineer or attempt to extract the source code from any API or any related software, except to the extent such use is expressly allowed by applicable law. 7. Use the APIs for any activities where the use or failure of the APIs could lead to death, personal injury, or environmental damage (such as the operation of nuclear facilities, air traffic control, or life support systems). 8. Use the APIs to submit to Realogy, or process or store, any data that (a) any information relating, directly or indirectly, to an identified or identifiable natural person located in the European Economic Area (“EEA”), Switzerland and/or the United Kingdom, and/or (b) is subject to the International Traffic in Arms Regulations maintained by the U.S. Department of State. 9. Remove, obscure, or alter any Realogy terms of service or any links to or notices of those terms. Unless otherwise specified in writing by Realogy, Realogy does not intend use of the APIs to create obligations under the Health Insurance Portability and Accountability Act, as amended ("HIPAA"), and makes no representations that the APIs satisfy HIPAA requirements. If you are (or become) a "covered entity" or "business associate" as defined in HIPAA, you will not use the APIs for any purpose or in any manner involving transmitting protected health information to Realogy unless you have received prior written consent to such use from Realogy.
View Source

Related to API Prohibitions

  • General Prohibitions Subject to and except as permitted by Sections 6.3(b) and 6.3(h), until the earlier of the termination of this Agreement pursuant to Article VIII hereof and the Effective Time, the Company shall not, nor shall it authorize or permit any of its Subsidiaries or any of its or their respective directors, officers or employees to, and the Company shall use its reasonable best efforts to cause its investment bankers, financial advisors, attorneys, accountants or other advisors, agents or representatives (collectively, “Representatives”) to, directly or indirectly, (i) solicit, initiate, or knowingly encourage or facilitate, any inquiries with respect to or the making of any proposal that constitutes or is reasonably likely to lead to a Takeover Proposal or any public announcement by any Third Party of any Takeover Proposal or of any intention to make the same, (ii) enter into or participate in any discussions or negotiations regarding any Takeover Proposal, furnish to any Third Party any non-public information (whether orally or in writing) in response to or in furtherance of any Takeover Proposal (for avoidance of doubt, it being hereby acknowledged and agreed that the foregoing shall not prohibit the Company or any of its Representatives from making any Third Party aware of the provisions of this Section 6.3 in response to any Takeover Proposal, nor shall the foregoing prohibit the Company from engaging in discussions with its Representatives to the extent necessary to assist the Company in determining how to comply with the provisions of this Section 6.3 and applicable Law), or afford any Third Party access to the business, properties, assets, books or records of the Company or any of its Subsidiaries, otherwise cooperate in any way with, or knowingly assist, participate in, facilitate or encourage any effort by, any Third Party that has made, or has informed the Company of any intention to make, or who has publicly announced an intention to make, a Takeover Proposal, (iii) recommend, adopt or approve, or publicly propose to recommend, adopt or approve, a Takeover Proposal, or fail to make in accordance with Section 6.1(a)(ii), withdraw or modify or resolve to take any action or make any public statement inconsistent with the Company Offer Recommendation or Company Merger Recommendation (any of the foregoing in this clause (iii), a “Company Adverse Recommendation Change”), (iv) take any action to make the provisions of any “fair price,” “moratorium,” “control share acquisition,” “business combination” or other similar anti-takeover statute or regulation (including approving any transaction for purposes of or approving a Third Party becoming an “interested stockholder” under Section 203 of the DGCL), or any restrictive provision of any applicable anti-takeover provision in the Company’s certificate of incorporation or bylaws, inapplicable to any transactions contemplated by a Takeover Proposal, (v) enter into any Takeover Proposal (other than a confidentiality agreement of the type referred to in Section 6.3(b)) or (vi) grant any Third Party any waiver or release under any standstill or similar agreement with respect to any class of equity securities of the Company or any of its Subsidiaries. Without limiting the foregoing, it is agreed that any violation of the restrictions on the Company set forth in the preceding sentence by any Representative of the Company or any of its Subsidiaries shall be a breach of this Section 6.3.

  • General Prohibition Without Landlord’s prior written consent subject to and on the conditions described in this Section 22, Tenant shall not, directly or indirectly, voluntarily or by operation of law, assign this Lease or sublease the Premises or any part thereof or mortgage, pledge, or hypothecate its leasehold interest or grant any concession or license within the Premises, and any attempt to do any of the foregoing shall be void and of no effect. If Tenant is a corporation, partnership or limited liability company, the shares or other ownership interests thereof which are not actively traded upon a stock exchange or in the over-the-counter market, a transfer or series of transfers whereby 50% or more of the issued and outstanding shares or other ownership interests of such corporation are, or voting control is, transferred (but excepting transfers upon deaths of individual owners) from a person or persons or entity or entities which were owners thereof at time of execution of this Lease to persons or entities who were not owners of shares or other ownership interests of the corporation, partnership or limited liability company at time of execution of this Lease, shall be deemed an assignment of this Lease requiring the consent of Landlord as provided in this Section 22.

  • Lobbying Prohibition Contractor represents and warrants that payments to Contractor and Contractor's receipt of appropriated or other funds under this Contract or any related Solicitation are not prohibited by Sections 556.005, 556.0055, or 556.008 of the Texas Government Code (relating to use of appropriated money or state funds to employ or pay lobbyists, lobbying expenses, or influence legislation).

  • Wildcard Prohibition For domain names which are either not registered, or the registrant has not supplied valid records such as NS records for listing in the DNS zone file, or their status does not allow them to be published in the DNS, the use of DNS wildcard Resource Records as described in RFCs 1034 and 4592 or any other method or technology for synthesizing DNS Resources Records or using redirection within the DNS by the Registry is prohibited. When queried for such domain names the authoritative name servers must return a “Name Error” response (also known as NXDOMAIN), RCODE 3 as described in ▇▇▇ ▇▇▇▇ and related RFCs. This provision applies for all DNS zone files at all levels in the DNS tree for which the Registry Operator (or an affiliate engaged in providing Registration Services) maintains data, arranges for such maintenance, or derives revenue from such maintenance.

  • Legal Prohibition No Law shall be in effect and no Order shall have been entered, in each case that restrains, enjoins or prohibits the performance of all or any part of this Agreement or the consummation of all or any part of the transactions contemplated by this Agreement, or declares unlawful the transactions contemplated by this Agreement or would cause any of the transactions contemplated by this Agreement to be rescinded.