Developer API Terms — iNTELIGENCIA VIVA

Draft — pending external legal review. This document sets out the product requirements and decisions that the final text must reflect; it has not been reviewed by a lawyer. It does not constitute legal advice and is not a publishable final version.

Last updated: [EFFECTIVE DATE]

1. Scope

These Developer API Terms ("API Terms") govern access to and use of iNTELIGENCIA VIVA's public REST API (v1) and its WebSocket streaming endpoint, by any Workspace or developer acting on its behalf ("You", the "Developer"). They supplement, and do not replace, the Terms of Service and the Acceptable Use Policy, which are incorporated here by reference.

2. Access and authentication

Access to the API requires an API key (APIKey) issued from the Workspace panel, with a permission scope configurable per key. Requests are authenticated with the Authorization: Bearer sk_live_... header. You are responsible for keeping your keys confidential; a compromised key must be revoked immediately from the panel. We will not disclose a key's full value after its creation, except to its owner at the moment of issuance.

3. Resources and versioning

In its v1 version, the API exposes the following resources: Workspace, Contact, Conversation, Message, Department, Agent, AIAgent, KnowledgeSource, Channel, Webhook, and APIKey. A WebSocket streaming endpoint (wss://api.inteligenciaviva.com/v1/workspaces/{id}/stream) allows consuming live events as an alternative or complement to webhooks.

We may add resources, fields, and events in a backward-compatible way without prior notice. Breaking changes will be introduced under a new API version, with a reasonable overlap period between versions and advance notice through the developer panel or the Workspace's registered email.

4. Rate limits

API access is subject to rate limits, publicly documented in the Developers section of the site and subject to periodic adjustment based on Service capacity and the Workspace's plan. Responses exceeding the limit are signaled with the corresponding HTTP status code (429) and current rate-limit headers; you are responsible for implementing a retry strategy with incremental backoff. Attempting to circumvent these limits constitutes a violation of the Acceptable Use Policy.

5. Webhooks

When you subscribe to outbound events (conversation.created, conversation.assigned, conversation.resolved, message.received, message.sent, handoff.requested, ai_agent.tool_call), each delivery is signed with HMAC using the secret associated with your WebhookEndpoint. You are responsible for verifying that signature before processing a delivery's content and for responding with a success status within a reasonable time; we will retry failed deliveries according to our current retry policy, without guaranteeing exactly-once delivery (at-least-once).

6. Permitted use of data obtained via the API

Data you obtain through the API — in particular Contact, Conversation, and Message data — belongs to the Workspace that issued the key used, and you may only use it for purposes that Workspace has authorized (for example, syncing with your own CRM, routing to an internal system, or tools invocable by an AIAgent). In particular, and without prejudice to the Acceptable Use Policy, you must not:

Use data obtained via the API to train or improve AI models that compete with iNTELIGENCIA VIVA.
Resell or redistribute that data to third parties not authorized by the relevant Workspace.
Retain that data beyond what is necessary for the authorized purpose, or store it with a lower level of security than required by the Data Processing Agreement, when you yourself act as a processor or sub-processor of the Workspace.

7. Access revocation

The Workspace owner may revoke any API key at any time from their panel, with immediate effect. We may also revoke or suspend the access of a key, a WebhookEndpoint, or a specific integration, without prior notice, when we detect use contrary to these API Terms, the Acceptable Use Policy, or a security risk to the Service or other Workspaces. Where reasonably possible, we will notify the affected Workspace owner of the revocation and its reason.

8. Availability and support

The API is offered at the same availability standard as the plan of the Workspace under which the key was issued; Enterprise plans may have a separate contractual service level agreement (SLA) for the API. Outside of that case, the API is offered on a best-effort basis, with no guaranteed uptime.

9. Compliance with the Acceptable Use Policy

All use of the API is subject to the Acceptable Use Policy, including its specific provisions on rate-limit circumvention, scraping, and using data to train competing models.

10. Liability

The API is provided "as is". To the maximum extent permitted by applicable law in Costa Rica, we do not warrant that the API will be error-free or uninterrupted, and our liability to you for API use is governed by the limits set out in the Terms of Service.

11. Changes to these API Terms

We may update these API Terms to reflect the platform's evolution. Material changes will be communicated with reasonable advance notice through the developer panel or by email.

12. Developer contact

Technical or legal questions about API use: developers@inteligenciaviva.com.