API Terms of Use

These API Terms of Use ('API Terms') govern your access to and integration with CapEngage Application Programming Interfaces (APIs), software development kits (SDKs), documentation, and webhooks ('CapEngage APIs').

By generating API keys, connecting OAuth integrations, or making HTTP calls to `api.capengage.com`, you agree to comply with these API Terms and our Master Terms of Service.

Access to CapEngage APIs requires valid authentication credentials (such as Secret API Keys or Bearer OAuth 2.0 Access Tokens).

• Key Confidentiality: API keys grant programmatic access to your customer database. You are solely responsible for keeping keys confidential. Do NOT embed API secret keys in client-side code, public repositories, or mobile app binaries. • Compromised Credentials: If an API key is exposed, you must revoke the key immediately in your dashboard and generate a new key pair.

To maintain service stability for all multi-tenant users, CapEngage enforces rate limits on API requests (e.g. 100 requests per second for standard tiers, expandable for Enterprise tiers).

Exceeding rate limits will result in HTTP `429 Too Many Requests` responses. Repeated attempt to bypass rate limits or conduct automated polling loops at excessive frequency may result in API token revocation.

CapEngage provides real-time outbound webhooks for customer event notifications (such as email opens, WhatsApp delivery receipts, link clicks, or AI agent lead qualification triggers).

• Webhook Signatures: Outbound webhooks include an `X-CapEngage-Signature` header containing an HMAC-SHA256 signature. Developers are required to verify webhook signatures to validate payload authenticity. • Retry Policy: Unresponsive endpoints (non-2xx HTTP responses) trigger automated exponential backoff retries over 24 hours before moving to a dead-letter queue.

CapEngage uses URI-based API versioning (e.g. `/v1/`, `/v2/`).

We provide at least ninety (90) days' advance written notice via email and developer documentation before deprecating a major API version or making breaking structural changes to API response schemas.