Common use of Application Programming Interface Provisions Clause in Contracts

Application Programming Interface Provisions. (a) In connection with its use of the Docebo Software, the Customer will be provided with access to an 'instance' or ‘deployment environment' of the Docebo Software (a "Docebo Instance"). The Docebo Instance may be accessible through an Application Program Interface (API) requiring login and API credentials (the "Docebo Credentials"). Docebo allows the Customer to control, track, and monitor End Users with access to the Docebo Credentials. (b) Docebo provides documentation disclosing certain protocols and aspects of its Docebo Software functionality for building and integrating Third Party Applications (the "API Protocols"), which may be updated from time to time provided however such change will not result in a material degradation of the Customer's ability to use the Services. Docebo expressly disclaims and shall have no liability with respect to how the API Protocols are used. Further, unless otherwise specified by the Parties, in writing in an applicable Order Form or SOW, Docebo takes no ownership interest in or rights to any third-party software code that incorporates the API Protocols. (c) In order to enable the functionality provided by the API Protocols, a requesting party must serve licensed Docebo Credentials to the Docebo Instance. The Customer expressly understands that Docebo does not go beyond a verification of proper Docebo Credentials to validate whether or not access to or use of a customer's Docebo Instance is authorized. Accordingly, an unauthorized party may use misappropriated, although valid, Docebo Credentials to gain access to and employ the functionality of an otherwise properly licensed Docebo Instance. Once the Docebo Credentials are validated by the Docebo Instance, any software code that is written in accordance with the API Protocols will function with the Docebo Instance as designed. Thus, any unauthorized dissemination and distribution of the Docebo Credentials may lead to an unauthorized use of a Docebo Instance. Docebo expressly disclaims and shall have no liability to the Customer, or any third-party, for any loss or damages resulting from how the API Protocols are used, unless and to the extent that the same may be solely and directly attributable to Docebo's actions.

Application Programming Interface Provisions. (a) In connection with its use of the Docebo Software, the Customer will may, in some operating environments, be provided with access to an 'instance' or ‘deployment environment' of the Docebo Software (a "Docebo Instance"). The Docebo Instance may be accessible through an Application Program Interface (API) requiring login and API credentials (the "Docebo Credentials"). Docebo allows the Customer Company to control, track, and monitor End Users with access to the Docebo API Credentials. (b) Docebo provides documentation disclosing certain protocols and aspects of its Docebo Software functionality for building and integrating Third Party Applications (the "API Protocols"), which may be updated from time to time provided however such change will not result in a material degradation of the Customer's ability to use the Software Services. Docebo expressly disclaims and shall have no liability with respect to how the API Protocols are used, except to the extent that it has directed the same. Further, unless otherwise specified by the Parties, in writing in an applicable Order Form or SOW, Docebo takes no ownership interest in or rights to any third-party software code that incorporates the API Protocols. (c) In order to enable the functionality provided by the API Protocols, a requesting party must serve licensed Docebo Credentials to the Docebo Instance. The Customer expressly understands that Docebo does not go beyond a verification of proper Docebo Credentials to validate whether or not access to or use of a customer's Docebo Instance is authorized. Accordingly, an unauthorized party may use misappropriated, although valid, Docebo Credentials to gain access to and employ the functionality of an otherwise properly licensed Docebo Instance. Once the Docebo Credentials are validated by the Docebo Instance, any software code that is written in accordance with the API Protocols will function with the Docebo Instance as designed. Thus, any unauthorized dissemination and distribution of the Docebo Credentials may lead to an unauthorized use of a Docebo Instance. Docebo expressly disclaims and shall have no liability to the CustomerCompany, or any third-third party, for any loss or damages resulting from how the API Protocols are used, unless and to the extent that the same may be solely and directly attributable to Docebo's actions.

Application Programming Interface Provisions. (a) In connection with its use of the Docebo Software, the Customer will may, in some operating environments, be provided with access to an 'instance' or ‘deployment environment' of the Docebo Software (a "Docebo Instance"). The Docebo Instance may be accessible through an Application Program Interface (API) requiring login and API credentials (the "Docebo Credentials"). Docebo allows the Customer to control, track, and monitor End Users with access to the Docebo API Credentials. (b) Docebo provides documentation disclosing certain protocols and aspects of its Docebo Software functionality for building and integrating Third Party Applications (the "API Protocols"), which may be updated from time to time provided however such change will not result in a material degradation of the Customer's ability to use the Services. Docebo expressly disclaims and shall have no liability with respect to how the API Protocols are used, except to the extent that it has directed the same. Further, unless otherwise specified by the Parties, in writing in an applicable Order Form or SOW, Docebo takes no ownership interest in or rights to any third-party software code that incorporates the API Protocols. (c) In order to enable the functionality provided by the API Protocols, a requesting party must serve licensed Docebo Credentials to the Docebo Instance. The Customer expressly understands that Docebo does not go beyond a verification of proper Docebo Credentials to validate whether or not access to or use of a customer's Docebo Instance is authorized. Accordingly, an unauthorized party may use misappropriated, although valid, Docebo Credentials to gain access to and employ the functionality of an otherwise properly licensed Docebo Instance. Once the Docebo Credentials are validated by the Docebo Instance, any software code that is written in accordance with the API Protocols will function with the Docebo Instance as designed. Thus, any unauthorized dissemination and distribution of the Docebo Credentials may lead to an unauthorized use of a Docebo Instance. Docebo expressly disclaims and shall have no liability to the Customer, or any third-third party, for any loss or damages resulting from how the API Protocols are used, unless and to the extent that the same may be solely and directly attributable to Docebo's actions.

Application Programming Interface Provisions. (a) In connection with its use of the Docebo SoftwareSoftware Services, the Customer will Company may, in some operating environments, be provided with access to an '‘instance' or ‘deployment environment' ’ of the Docebo Software (a "“Docebo Instance"”). The Docebo Instance may be accessible through an Application Program Interface (API) requiring login and API credentials (the "Docebo Credentials"). Docebo allows the Customer to control, track, and monitor End Users with access to the Docebo Credentials.Program (b) Docebo provides documentation disclosing certain protocols and aspects of its software functionality (“API Software and Protocols”). The API Software and Protocols may allow customers to pull and insert specific data elements into and out of their Docebo Software functionality for building and integrating Third Party Applications instance (the "API Protocols"“Code Snippet”), which may be updated from time to time provided however such change will not result in a material degradation of the Customer's ability to use the Services. Docebo expressly disclaims and shall have no liability with respect to how the API Software and Protocols or Code Snippets are used. Further, unless otherwise specified by the Parties, in writing in an applicable Order Form or SOW, Docebo takes no ownership interest in or rights to any third-party software code that incorporates the API ProtocolsSoftware and Protocols or Code Snippets, unless otherwise agreed by the parties upon in writing. (c) In order to enable the functionality provided by the API Software and Protocols, a requesting party must serve licensed Docebo Credentials to the Docebo Instance. The Customer Company expressly understands that Docebo does not go beyond a verification of proper Docebo Credentials to validate whether or not access to or use of a customer's ’s Docebo Instance is authorized. Accordingly, an unauthorized party may use misappropriated, although valid, Docebo Credentials to gain access to and employ the functionality of an otherwise properly licensed Docebo Instance. Once the Docebo Credentials are validated by the Docebo Instance, any software code that is written in accordance with the to Docebo’s API Protocols will function with the Docebo Instance as designed. Thus, any unauthorized dissemination and distribution of the Docebo Credentials may lead to an unauthorized use of a Docebo Instance. Docebo expressly disclaims and shall have no liability to the Customer, Company or any thirdthird party for how the API Software and Protocols or Code Snippets are used, whether authorized or not authorized by Company. (d) Docebo allows Company to control, track, and monitor end-partyusers with access to the API credentials. Company expressly understands and acknowledges, therefore, that it is an obligation upon Company to govern all End Users under its license with policies and procedures that conform to an authorized use of their subscribed Docebo Instance. (e) Nothing in the foregoing shall be construed as a requirement on Docebo to follow the same API Software and Protocols in the future, and the parties expressly understand that Docebo may change the API Software and Protocols, with or without notice, at any time. Docebo shall have no liability to Company or any third party with respect to any changes, whether announced or unannounced. (f) Docebo expressly disclaims and shall have no liability for any loss or damages resulting from how the use of the API Protocols are usedSoftware and Protocols, unless with or without misappropriated API Credentials in a software application, and Company shall indemnify defend, and hold harmless Docebo against all claims, actions or proceedings, arising out of any claim related thereto, to the extent that the same may be solely and directly attributable to Docebo's actionsof Company’s action or inaction with respect thereto.

Application Programming Interface Provisions. (a) In connection with its use of the Docebo SoftwareSoftware Services, the Customer will Company may, in some operating environments, be provided with access to an '‘instance' or ‘deployment environment' ’ of the Docebo Software (a "“Docebo Instance"”). The Docebo Instance may be accessible through an Application Program Interface (API) requiring login and API credentials (the "“Docebo Credentials"”). The Company expressly understands and agrees that Docebo allows the Customer to does not control, track, and or monitor End Users with access to the dissemination of any of “Docebo Credentials”, and, therefore, any misappropriation of those Docebo Credentials may neither be apparent to nor discoverable by Docebo without notice. (b) Docebo provides documentation disclosing certain protocols and aspects of its Docebo Software software functionality for building and integrating Third Party Applications (the "“API Software and Protocols"”). The API Software and Protocols may allow Docebo customers to pull and insert specific data elements into and out of their Docebo Instance (each, which may be updated from time to time provided however such change will not result in a material degradation of the Customer's ability to use the Services“Code Snippet”). Docebo expressly disclaims and shall have no liability with respect to how the API Software and Protocols or Code Snippets are used, except to the extent that it has directed the same. Further, unless otherwise specified by the Parties, in writing in an applicable Order Form or SOW, Docebo takes no ownership interest in or rights to any third-party software code that incorporates the API ProtocolsSoftware and Protocols or Code Snippets. (c) In order to enable the functionality provided by the API Software and Protocols, a requesting party must serve licensed Docebo Credentials to the Docebo Instance. The Customer Company expressly understands that Docebo does not go beyond a verification of proper Docebo Credentials to validate whether or not access to or use of a customer's ’s Docebo Instance is authorized. Accordingly, an unauthorized party may use misappropriated, although valid, Docebo Credentials to gain access to and employ the functionality of an otherwise properly licensed Docebo Instance. Once the Docebo Credentials are validated by the Docebo Instance, any software code that is written in accordance with to the API Software and Protocols will function with the Docebo Instance as designed. Thus, any unauthorized dissemination and distribution of the Docebo Credentials may lead to an unauthorized use of a Docebo Instance. Docebo expressly disclaims and shall have no liability to the CustomerCompany, or any third-third party, for any loss or damages resulting from how the API Software and Protocols or Code Snippets are used, whether authorized or not authorized by Company, unless and to the extent that the same may be solely and directly attributable to Docebo's ’s actions. (d) Docebo allows the Company to control, track, and monitor End Users with access to the API Credentials. The Company expressly understands and acknowledges, therefore, that it is an obligation upon the Company to govern all End Users under its license with policies and procedures that conform to an authorized use of their subscribed Docebo Instance. (e) Nothing in the foregoing shall be construed as a requirement on Docebo to follow the same API Software and Protocols in the future, and the Parties expressly understand that Docebo may change the API Software and Protocols, with reasonable advanced notice, at any time. Docebo shall have no liability to the Company or any third party with respect to any such changes; provided, however, that, in the event that any such change results in a material degradation of the Company’s ability to use the Services, the Company may terminate such Services without further liability.

Application Programming Interface Provisions. (a) In connection with its use of the Docebo SoftwareSoftware Services, the Customer will Company may, in some operating environments, be provided with access to an '‘instance' or ‘deployment environment' ’ of the Docebo Software (a "“Docebo Instance"”). The Docebo Instance may be accessible through an Application Program Interface (API) requiring login and API credentials (the "“Docebo Credentials"”). Docebo allows the Customer to The Company expressly understands and agrees that Xxxxxx does not control, track, and or monitor End Users with access to the dissemination of any of “Docebo Credentials”, and, therefore, any misappropriation of those Docebo Credentials may neither be apparent to nor discoverable by Docebo without notice. (b) Docebo provides documentation disclosing certain protocols and aspects of its Docebo Software software functionality for building and integrating Third Party Applications (the "“API Software and Protocols"”). The API Software and Protocols may allow Docebo customers to pull and insert specific data elements into and out of their Docebo Instance (each, which may be updated from time to time provided however such change will not result in a material degradation of the Customer's ability to use the Services“Code Snippet”). Docebo expressly disclaims and shall have no liability with respect to how the API Software and Protocols or Code Snippets are used, except to the extent that it has directed the same. Further, unless otherwise specified by the Parties, in writing in an applicable Order Form or SOW, Docebo takes no ownership interest in or rights to any third-party software code that incorporates the API ProtocolsSoftware and Protocols or Code Snippets. (c) In order to enable the functionality provided by the API Software and Protocols, a requesting party must serve licensed Docebo Credentials to the Docebo Instance. The Customer Company expressly understands that Docebo does not go beyond a verification of proper Docebo Credentials to validate whether or not access to or use of a customer's ’s Docebo Instance is authorized. Accordingly, an unauthorized party may use misappropriated, although valid, Docebo Credentials to gain access to and employ the functionality of an otherwise properly licensed Docebo Instance. Once the Docebo Credentials are validated by the Docebo Instance, any software code that is written in accordance with to the API Software and Protocols will function with the Docebo Instance as designed. Thus, any unauthorized dissemination and distribution of the Docebo Credentials may lead to an unauthorized use of a Docebo Instance. Docebo expressly disclaims and shall have no liability to the CustomerCompany, or any third-third party, for any loss or damages resulting from how the API Software and Protocols or Code Snippets are used, whether authorized or not authorized by Company, unless and to the extent that the same may be solely and directly attributable to Docebo's ’s actions. (d) Docebo allows the Company to control, track, and monitor End Users with access to the API Credentials. The Company expressly understands and acknowledges, therefore, that it is an obligation upon the Company to govern all End Users under its license with policies and procedures that conform to an authorized use of their subscribed Docebo Instance. (e) Nothing in the foregoing shall be construed as a requirement on Docebo to follow the same API Software and Protocols in the future, and the Parties expressly understand that Docebo may change the API Software and Protocols, with reasonable advanced notice, at any time. Docebo shall have no liability to the Company or any third party with respect to any such changes; provided, however, that, in the event that any such change results in a material degradation of the Company’s ability to use the Services, the Company may terminate such Services without further liability.

Application Programming Interface Provisions. (a) In connection with its use of the Docebo SoftwareSoftware Services, the Customer will Company may, in some operating environments, be provided with access to an 'instance' or ‘deployment environment' instance of the Docebo Software (a "( Docebo Instance"Instance ). The .The Docebo Instance may be accessible through an Application Program Interface (API) requiring login and API credentials (the "Docebo Credentials"). Docebo allows the Customer to control, track, and monitor End Users with access to the Docebo Credentials.Program (b) Docebo provides documentation disclosing certain protocols and aspects of its software functionality ( API Software and Protocols ). The API Software and Protocols may allow customers to pull and insert specific data elements into and out of their Docebo Software functionality for building and integrating Third Party Applications (the "API Protocols"instance ( Code Snippet ), which may be updated from time to time provided however such change will not result in a material degradation of the Customer's ability to use the Services. Docebo expressly disclaims and shall have no liability with respect to how the API Software and Protocols or Code Snippets are used. Further, unless otherwise specified by the Parties, in writing in an applicable Order Form or SOW, Docebo takes no ownership interest in or rights to any third-party software code that incorporates the API ProtocolsSoftware and Protocols or Code Snippets, unless otherwise agreed by the parties upon in writing. (c) In order to enable the functionality provided by the API Software and Protocols, a requesting party must serve licensed Docebo Credentials to the Docebo Instance. The Customer Company expressly understands that Docebo does not go beyond a verification of proper Docebo Credentials to validate whether or not access to or use of a customer's customer s Docebo Instance is authorized. Accordingly, an unauthorized party may use misappropriated, although valid, Docebo Credentials to gain access to and employ the functionality of an otherwise properly licensed Docebo Instance. Once the Docebo Credentials are validated by the Docebo Instance, any software code that is written in accordance with the to Docebo s API Protocols will function with the Docebo Instance as designed. Thus, any unauthorized dissemination and distribution of the Docebo Credentials may lead to an unauthorized use of a Docebo Instance. Docebo expressly disclaims and shall have no liability to the Customer, Company or any thirdthird party for how the API Software and Protocols or Code Snippets are used, whether authorized or not authorized by Company. (d) Docebo allows Company to control, track, and monitor end-partyusers with access to the API credentials. Company expressly understands and acknowledges, therefore, that it is an obligation upon Company to govern all End Users under its license with policies and procedures that conform to an authorized use of their subscribed Docebo Instance. (e) Nothing in the foregoing shall be construed as a requirement on Docebo to follow the same API Software and Protocols in the future, and the parties expressly understand that Docebo may change the API Software and Protocols, with or without notice, at any time. Docebo shall have no liability to Company or any third party with respect to any changes, whether announced or unannounced. (f) Docebo expressly disclaims and shall have no liability for any loss or damages resulting from how the use of the API Protocols are usedSoftware and Protocols, unless with or without misappropriated API Credentials in a software application, and Company shall indemnify defend, and hold harmless Docebo against all claims, actions or proceedings, arising out of any claim related thereto, to the extent that the same may be solely and directly attributable to Docebo's actionsof Company s action or inaction with respect thereto.

Application Programming Interface Provisions. (a) In connection with its use of the Docebo Software, the Customer will may be provided with access to an 'instance' or ‘deployment environment' of the Docebo Software (a "Docebo Instance"). The Docebo Instance may be accessible through an Application Program Interface (API) requiring login and API credentials (the "Docebo Credentials"). Docebo allows the Customer to control, track, and monitor End Users with access to the Docebo Credentials. (b) Docebo provides documentation disclosing certain protocols and aspects of its Docebo Software functionality for building and integrating Third Party Applications (the "API Protocols"), which may be updated from time to time provided however such change will not result in a material degradation of the Customer's ability to use the Services. Docebo expressly disclaims and shall have no liability with respect to how the API Protocols are used, except to the extent that it has directed the same. Further, unless otherwise specified by the Parties, in writing in an applicable Order Form or SOW, Docebo takes no ownership interest in or rights to any third-party software code that incorporates the API Protocols. (c) In order to enable the functionality provided by the API Protocols, a requesting party must serve licensed Docebo Credentials to the Docebo Instance. The Customer expressly understands that Docebo does not go beyond a verification of proper Docebo Credentials to validate whether or not access to or use of a customer's Docebo Instance is authorized. Accordingly, an unauthorized party may use misappropriated, although valid, Docebo Credentials to gain access to and employ the functionality of an otherwise properly licensed Docebo Instance. Once the Docebo Credentials are validated by the Docebo Instance, any software code that is written in accordance with the API Protocols will function with the Docebo Instance as designed. Thus, any unauthorized dissemination and distribution of the Docebo Credentials may lead to an unauthorized use of a Docebo Instance. Docebo expressly disclaims and shall have no liability to the Customer, or any third-party, for any loss or damages resulting from how the API Protocols are used, unless and to the extent that the same may be solely and directly attributable to Docebo's actions.

Application Programming Interface Provisions. (a) In connection with its use of the Docebo Software, the Customer will may, in some operating environments, be provided with access to an 'instance' or ‘deployment environment' of the Docebo Software (a "Docebo Instance"). The Docebo Instance may be accessible through an Application Program Interface (API) requiring login and API credentials (the "Docebo Credentials"). Docebo allows the Customer to control, track, and monitor End Users with access to the Docebo API Credentials. (b) Docebo Omniplex provides documentation disclosing certain protocols and aspects of its Docebo Software functionality for building and integrating Third Party Applications (the "API Protocols"), which may be updated from time to time provided however such change will not result in a material degradation of the Customer's ability to use the Services. Docebo Omniplex expressly disclaims and shall have no liability (whether in contract, tort (including negligence) breach of statutory duty or otherwise howsoever arising) with respect to how the API Protocols are used, except to the extent that it has directed the same. Further, unless otherwise specified by the Parties, in writing in an applicable Order Form or SOW, Docebo Omniplex takes no ownership interest in or rights to any third-party software code that incorporates the API Protocols. (c) In order to enable the functionality provided by the API Protocols, a requesting party must serve licensed Docebo Credentials to the Docebo Instance. The Customer expressly understands that Docebo Omniplex does not go beyond a verification of proper Docebo Credentials to validate whether or not access to or use of a customer's Docebo Instance is authorized. Accordingly, an unauthorized party may use misappropriated, although valid, Docebo Credentials to gain access to and employ the functionality of an otherwise properly licensed Docebo Instance. Once the Docebo Credentials are validated by the Docebo Instance, any software code that is written in accordance with the API Protocols will function with the Docebo Instance as designed. Thus, any unauthorized dissemination and distribution of the Docebo Credentials may lead to an unauthorized use of a Docebo Instance. Docebo Omniplex expressly disclaims and shall have no liability (whether in contract, tort (including negligence) breach of statutory duty or otherwise howsoever arising) to the Customer, or any third-third party, for any loss or damages resulting from how the API Protocols are used, unless and to the extent that the same may be solely and directly attributable to DoceboOmniplex's actions.