API and SDK Terms

Intelligence Cloud API and SDK Terms

The terms for using the Intelligence Cloud API, webhooks and SDKs, in plain English. They sit under the agreement you already have with Tresic or with your provider.

Version 1.0November 2026Effective 17 November 2026
Section 1

Who these terms apply to

PartnersCustomersDevelopers and contractors
Note

These terms supplement your agreement with Tresic or your provider.

These API and SDK Terms ("Terms") are issued by Creo Solutions, Inc., a Delaware corporation, d/b/a Tresic ("Tresic", "we"). They apply to anyone who uses the Intelligence Cloud API, its webhooks, the SDKs or the samples in the Intelligence Cloud documentation ("you").

You areHow these Terms apply
A Tresic partnerThese Terms supplement your Reseller & White Label Agreement with Tresic and its Data Processing Addendum (together, "the Agreement").
A partner's customer, or a contractor working for a partner or a customerThese Terms apply to you through the partner. The partner must flow them down to its customers and contractors, and is responsible to Tresic for their use of the API.

Order of precedence. If these Terms conflict with the Agreement, the Agreement wins. Capitalised terms not defined here have the meaning the Agreement gives them.

Section 2

Access and credentials

  • Your accounts are your responsibility. You are responsible for everything done with your users' credentials, tokens and webhook addresses, and for keeping them secret.
  • Dedicated integration users. An integration signs in as a user created for that integration alone, named for its purpose, never as a person's own account. One integration user per purpose.
  • API keys. When API keys are available, use them for server-to-server calls on the same terms.
  • Documented access only. Access the service programmatically only through the documented API, as the API and Integration Guide and the API reference describe it.
Section 3

Acceptable use

The use restrictions in Section 2.2 of the Agreement, including Section 2.2.3 (Automated Agents and Data Scraping), and the Acceptable Use and Prohibited Conduct exhibit (Exhibit B) are part of these Terms and apply to every use of the API. In addition, you will not:

  1. Poll for new data. Use the webhooks for anything that must happen as calls and alerts arrive, and read the API on demand or in scheduled jobs as the API and Integration Guide describes.
  2. Exceed rate limits. Respect the published limits, and on a 429 response back off and honour Retry-After.
  3. Circumvent access controls, or try to reach accounts, data or locations your credentials are not authorised for.
  4. Reverse engineer the service, including how analysis, sentiment, topics or alerts are produced, whether from the service itself or from its outputs.
  5. Train, adapt or benchmark third-party AI models on outputs of the service.
  6. Give a third party's automated agent access to the service, by any credential or session, to scrape, harvest or bulk-extract data, outputs or content.

Permitted: a customer's own scheduled export of its own data, for its own operational and business-intelligence use, through the documented API.

Section 4

Data protection

  • The Data Processing Addendum governs Tresic's processing of personal information.
  • Health information is processed only under a business associate agreement (BAA). Tresic signs a BAA with every partner that processes health information with Tresic. The partner holds a BAA with its healthcare customer and with every downstream system that receives health information from an integration.
  • The protection rules in Conversation data protection are part of these Terms.
  • Incidents. Report any suspected exposure of conversation data or credentials to security@tresic.cloud within 24 hours of discovering it. Tresic notifies its partner as the Data Processing Addendum sets out, and the partner notifies its customer.
Section 6

Automated output: a person decides

Summaries, sentiment, topics, tasks and alerts are produced automatically from each call and can be wrong. Use them to find and route work; a person makes any decision with medical, legal, financial or employment consequences.

Section 7

Webhooks

The customer controls its webhook receivers and is responsible for securing them and for the data they receive. Tresic may pause or disable an endpoint that keeps failing, refuses deliveries or puts the service at risk.

Section 8

Rate limits

Rate limits are published in the API and Integration Guide's Rate limits table. Tresic may throttle or suspend an integration to protect the service.

Section 9

Changes to the API

v1 is stable. We add fields, endpoints and enum values at any time, without notice: ignore unknown fields and treat unknown enum values as "other". We give at least 90 days' notice by email to partner contacts, and in the API and Integration Guide's changelog, before removing or changing documented behaviour, except where a security, legal or abuse reason requires a faster change. Undocumented behaviour may change at any time.

Section 10

SDKs and samples

The SDKs are governed by the Intelligence Cloud SDK Licence in each package. Code samples in the Intelligence Cloud documentation, including the Integration Recipes, are provided as is, for you to adapt.

Section 11

Feedback

If you send us suggestions or feedback about the API, the SDKs or the documentation, we may use them without obligation to you.

Section 12

Suspension and termination

  • Suspension. Tresic may suspend or revoke a credential, token, key, session or webhook that it reasonably believes breaks these Terms or puts the service, its users or their data at risk, and will tell the partner as soon as practicable.
  • Termination. Your right to use the API ends when your access to Intelligence Cloud ends under the Agreement, or when your partner or Tresic ends it. On termination, stop using the API and delete credentials and data as the Agreement and the protection rules require.
Section 13

Warranty and liability

The API, webhooks, SDKs, samples and the documentation come with no warranty beyond what the applicable agreement provides. Service levels are those of the applicable agreement only. Tresic's liability is limited as the applicable agreement provides; where you have no agreement with Tresic, your recourse is under your agreement with your provider.

Section 14

Export control and sanctions

You will comply with US export control and economic sanctions laws and those that apply to you. You will not use the API, or let anyone use it, in a sanctioned country or region, or for or on behalf of a person on a US or other applicable restricted-party list.

Section 15

Trademarks

Tresic, Intelligence Cloud and the Tresic product names are trademarks of Tresic. Use them only as the Agreement allows. Other names in the documentation are trademarks of their respective owners.

Section 16

Security research

Report vulnerabilities as the Vulnerability Disclosure Policy describes. Good-faith security research that follows that policy does not breach these Terms.

Section 17

Changes to these Terms

We may update these Terms. We publish each version on this page with its version number and effective date, and tell partners by email before a material change takes effect. Continuing to use the API after a change takes effect means you accept it.

Section 18

Contact

You needGo to
Help with the API or these Termssupport@tresic.cloud, or your provider
A security incident or a vulnerabilitysecurity@tresic.cloud
Creo Solutions, Inc. d/b/a Tresic © 2026 Creo Solutions, Inc. d/b/a Tresic · API and SDK Terms · Other names are trademarks of their respective owners.