API Terms

By accessing or using Oration’s APIs, SDKs or other associated software ( collectively, “APIs”), you are agreeing to the terms below ( the “API Terms”), in addition to any terms agreed to in a Services Agreement and/or Oration’s Terms of Use (“Agreement”). Any capitalized terms in these API Terms will have the same meaning as set out in the Agreement. If you are using the APIs on behalf of an entity, you represent and warrant that you have authority to bind that entity to the Terms and by accepting the Terms, you are doing so on behalf of that entity (and all references to “you” in the Terms refer to that entity).

1. Use of the Oration Support API. Subject to Customer’s compliance with the terms and conditions hereunder, Customer may use the Oration Support APIs solely: (a) in accordance with these API Terms and the Oration Support API Documentation; and (b) to facilitate Customer’s use of the Platform Services.
2. API Credentials Required to Access the Oration Support API. Certain authenticated features and functionality available through the Oration Support API may require an authentication key. If Customer wishes to access these features, Customer may be required to generate one or more Customer ID, OAuth authorizations or API keys (each, an “API Credential”). Customer acknowledges and agrees that it is Customer’s responsibility to keep Customer’s API Credentials secure and confidential.
3. Licence to the Oration Support API Documentation. We hereby grant to Customer a revocable, non-exclusive, non-sublicensable, non-transferable license to access and use the Oration Support API Documentation solely to facilitate Customer’s use of applications that interface with our products and services in accordance with these API Terms, the Agreement, and the Oration Support API Documentation (each such application, an “Application”).
4. API Call Limitations. The number of calls Customer or Customer’s Application makes to the Oration Support API during any given period may be limited, at our sole discretion, based on various factors, including the manner in which Customer’s Application makes calls to the Oration Support API and the anticipated volume of use associated with Customer’s Application.
5. Changes to the Oration Support API and Oration Support API Documentation. We reserve the right to change the Oration Support API and Oration Support API Documentation at any time and without notice. Customer acknowledges and understands that these changes may require Customer to make substantial changes to Customer’s Application at Customer’s own cost and expense. It is Customer’s responsibility to review the Oration Support API Documentation regularly.
6. Monitoring Usage of API. Customer acknowledges and agrees that Oration Support we may monitor Customer’s use of the Oration Support API and that Customer will not block or otherwise interfere with our monitoring.