On this page
Developer access is conditional: these Terms apply only to developer functionality that tealsi actually makes available to you. Publication of these Terms does not mean that every Customer has access to a public API, SDK, webhook system or developer program.
API KEYS, TOKENS, CLIENT SECRETS, WEBHOOK SECRETS AND OTHER DEVELOPER CREDENTIALS ARE CUSTOMER RESPONSIBILITIES. CUSTOMER IS RESPONSIBLE FOR ACTIVITY PERFORMED USING CREDENTIALS ISSUED TO OR CONTROLLED BY CUSTOMER UNTIL TEALSI IS NOTIFIED OF COMPROMISE AND THE CREDENTIAL IS REVOKED OR REPLACED.
1. Scope and Applicability
These API & Developer Terms (“Developer Terms”) govern access to and use of application programming interfaces, API keys, access tokens, webhooks, SDKs, developer documentation, integration credentials, sandbox functionality and other programmatic tools that tealsi may make available (“Developer Services”).
These Developer Terms form part of and are incorporated into the Terms of Service. They also incorporate the Acceptable Use Policy, Privacy Policy, Data Processing Addendum and other applicable policies.
2. No Promise of Public API Availability
Publication of these Developer Terms does not constitute a commitment that tealsi offers a public API, unrestricted developer access, a particular endpoint, a particular SDK or any specific developer feature.
Developer Services may be limited to selected plans, Customers, approved integrations, beta participants or other users designated by tealsi.
3. Limited API and Developer License
Subject to Customer’s compliance with these Developer Terms and the Terms of Service, tealsi grants Customer a limited, revocable, non-exclusive, non-transferable right to use the Developer Services solely to access and interact with tealsi in the manner expressly authorized by tealsi.
No rights are granted by implication. tealsi may limit the scopes, endpoints, actions, data or environments available to Customer.
4. API Keys, Tokens and Credentials
Customer must keep API keys, OAuth credentials, refresh tokens, access tokens, client secrets, webhook signing secrets and other developer credentials confidential and secure.
Customer must not publish credentials in public repositories, client-side code, websites, documentation, screenshots, forums or other locations where unauthorized persons may obtain them.
Customer may not sell, lease, sublicense, transfer or share developer credentials except with Authorized Users or contractors who require access for Customer’s permitted use and are bound by appropriate confidentiality and security obligations.
5. Security Requirements
Customer must implement reasonable technical and organizational safeguards appropriate to the sensitivity of the Developer Services and data accessed.
Such safeguards may include secret management, encryption, access restrictions, least-privilege permissions, secure storage, credential rotation, logging, monitoring and prompt revocation of compromised credentials.
6. Rate Limits and Technical Restrictions
tealsi may establish and enforce request limits, concurrency limits, quotas, storage limits, payload restrictions, execution limits, webhook limits, call frequency limits and other technical controls.
Customer may not circumvent, evade, defeat or artificially distribute traffic to avoid a rate limit or other technical restriction.
tealsi may modify limits at any time for security, reliability, provider, operational, commercial or abuse-prevention reasons.
7. Permitted Uses
Developer Services may be used to build legitimate integrations, internal tools, Customer applications, workflow connections and other uses that comply with the documentation, these Developer Terms and applicable law.
Customer must use Developer Services only within the permissions and scopes expressly granted.
8. Prohibited Developer Conduct
Customer may not use Developer Services to:
- circumvent tealsi pricing, usage metering, Wallet deductions, plan limitations or access controls;
- scrape, harvest or extract data outside authorized API methods or permissions;
- probe, scan, test or exploit vulnerabilities without written authorization;
- reverse engineer or attempt to derive non-public source code, internal APIs or proprietary protocols except where applicable law expressly prohibits restriction;
- interfere with Platform performance, infrastructure or other Customers;
- create malicious software, phishing systems, spam tools, credential-stuffing tools or abusive automation;
- use developer access to violate third-party rights, privacy rights, communications laws or provider rules;
- misrepresent Customer’s identity, application or relationship with tealsi; or
- resell standalone access to tealsi Developer Services unless expressly authorized in writing.
9. Customer Data and Personal Information
Customer is responsible for all Customer Data and personal information accessed, transmitted, stored or otherwise processed through Customer’s application or integration.
Customer must process data only for lawful and authorized purposes and must maintain appropriate privacy notices, consents, contracts and data-protection practices.
Where tealsi processes Customer Data on Customer’s behalf, the Data Processing Addendum applies as provided there.
10. Consent and Legal Compliance
Customer is responsible for obtaining all permissions, authorizations and consents required for data obtained from or sent to tealsi through Developer Services.
Developer access does not make an otherwise unlawful communication, data transfer, automated decision, call, message or marketing activity lawful.
11. Webhooks and Automated Events
tealsi may make webhooks or event notifications available. Customer is responsible for securing Customer’s webhook endpoint, validating signatures where supported, preventing replay attacks, processing events idempotently where appropriate and protecting data delivered through webhooks.
Webhooks may be delayed, duplicated, reordered, retried or fail to arrive. Customer should not design a critical workflow on the assumption that every event will be delivered exactly once or instantaneously unless tealsi expressly states otherwise.
12. Third-Party APIs and Connected Services
Developer Services may interact with third-party services, APIs, telecommunications carriers, payment processors, AI providers and connected accounts.
Customer remains responsible for complying with the terms and technical rules applicable to any third-party service Customer uses or connects.
Third-party changes may break or limit an integration without advance notice to tealsi.
13. Changes, Deprecation and Versioning
tealsi may add, change, version, deprecate, replace or discontinue endpoints, schemas, fields, events, authentication methods or other Developer Services.
Where reasonably practicable, tealsi may provide migration information or advance notice for material planned deprecations, but emergency, provider-driven, security or legal changes may occur with little or no advance notice.
14. Documentation and Examples
Developer documentation, code samples, examples, schemas and implementation guidance are provided for convenience and may contain errors or become outdated.
Customer is responsible for testing its implementation and should not treat sample code or documentation as a warranty of performance, security, legal compliance or suitability for Customer’s use case.
15. Availability and No SLA
Developer Services are provided on an “AS IS” and “AS AVAILABLE” basis. tealsi does not guarantee uninterrupted API availability, constant latency, backward compatibility, successful webhook delivery or permanent availability of any endpoint or feature.
Unless separately agreed in writing, no service-level agreement applies to Developer Services.
16. Monitoring, Logging and Abuse Detection
tealsi may monitor API requests, authentication events, errors, volume, rate-limit activity, webhook events and related technical information for security, billing, support, abuse detection, performance and compliance purposes.
tealsi is not obligated to pre-approve every Customer application or API request.
17. Suspension or Revocation of Developer Access
tealsi may restrict, throttle, suspend or revoke Developer Services immediately where tealsi reasonably believes Customer activity:
- violates these Developer Terms or another tealsi policy;
- creates security, fraud, abuse, provider or infrastructure risk;
- exceeds authorized scopes or limits;
- attempts to avoid usage fees or technical controls;
- threatens Platform availability or other Customers; or
- may violate applicable law.
18. Fees and Usage Charges
Developer Services may be subject to subscription restrictions, separate fees, API usage fees, telecommunications charges, AI consumption charges, Wallet deductions or other usage-based pricing.
Customer remains responsible for valid charges generated by Customer’s application, credentials, Authorized Users and Customer Clients, subject to the Wallet & Usage-Based Services Terms.
19. Intellectual Property
tealsi and its licensors retain all right, title and interest in Developer Services, APIs, documentation, schemas, SDKs, Platform technology and related intellectual property.
Customer retains rights in Customer’s independently created application code, subject to tealsi and third-party rights in underlying services and materials.
20. Feedback
If Customer provides ideas, suggestions, bug reports, improvements or other feedback regarding Developer Services, Customer grants Constellation X, LLC a worldwide, perpetual, irrevocable, royalty-free right to use and incorporate that feedback without restriction or compensation, to the extent permitted by law.
21. Customer Applications and End Users
Customer is solely responsible for any application, integration, software or service Customer builds using Developer Services (“Customer Application”).
Customer is responsible for Customer Application security, functionality, privacy, support, legal compliance, disclosures and interactions with End Users.
tealsi does not become a party to Customer’s relationship with Customer Application users merely because Developer Services are used.
22. Agencies and Customer Clients
If Customer is an agency, consultant or organization using Developer Services for Customer Clients, Customer remains responsible to tealsi for activity conducted through Customer’s credentials, integrations, subaccounts and Customer Applications.
Customer must ensure that Customer Clients are subject to terms sufficient to require lawful, secure and policy-compliant use.
23. Security Incidents and Credential Compromise
Customer must notify tealsi promptly if Customer knows or reasonably suspects that a developer credential has been exposed, stolen, compromised or used without authorization.
tealsi may revoke, rotate or disable credentials where necessary to protect the Platform. Customer is responsible for updating Customer Applications following credential rotation or revocation.
24. Beta and Experimental Developer Features
Developer Services identified as beta, preview, experimental, sandbox, early access or similar are provided for evaluation and may be incomplete, unstable, changed substantially or discontinued at any time.
Customer should not rely on beta functionality for mission-critical production use unless tealsi expressly agrees otherwise in writing.
25. Disclaimers
To the maximum extent permitted by law, Developer Services are provided without warranties of uninterrupted availability, merchantability, fitness for a particular purpose, non-infringement, error-free operation, compatibility or future availability.
26. Liability and Indemnification
Customer’s use of Developer Services remains subject to the limitation-of-liability and indemnification provisions in the Terms of Service.
Without limiting those provisions, Customer is responsible for claims arising from Customer Applications, Customer’s misuse of Developer Services, unauthorized data processing, security failures under Customer’s control, Customer communications or Customer’s violation of law or third-party rights.
27. Termination Effects
Upon termination or revocation of Developer Services, Customer must stop using affected credentials and endpoints and must comply with any applicable data deletion, retention or migration obligations.
tealsi may invalidate credentials and block further requests after termination.
28. Changes to these Developer Terms
tealsi may update these Developer Terms as Developer Services, security requirements, pricing, providers, laws or technical practices evolve.
Material changes may be communicated through the website, Platform, documentation, developer portal, email or another commercially reasonable method.
29. Contact
Questions about Developer Services or these Developer Terms may be directed to support@tealsi.com.
Build securely. Stay inside the permissions granted.
Developer access extends tealsi programmatically, but Customers remain responsible for credentials, applications, data use, security, End Users and compliance.