Skip to main content

Security controls are layered across identity, data, and operations.

Identity and access controls

  • Separate auth mechanisms for JWT, tenant API keys, partner API keys, and runtime server keys.
  • Scope-based API key authorization with explicit route-family permissions.
  • Tenant-aware authorization boundaries with optional tenant-context header where supported.
  • Least-privilege key issuance and periodic scope reviews recommended for all customers.

Data protection controls

  • TLS in transit for API and webhook communication.
  • Access-controlled storage and retrieval for call artifacts.
  • Environment isolation model for sandbox versus production data handling.
  • Configurable data lifecycle controls via retention and export workflows.

Operational security controls

  • Request IDs and structured logs for incident triage.
  • Retry-safe webhook patterns and dedupe guidance to reduce side-effect risks.
  • Controlled rollout guidance for production campaign activation.
  • Key rotation and revocation support through API key management endpoints.

Incident handling and support flow

1

Detect

Monitor auth failures, webhook processing anomalies, and runtime error rates.
2

Contain

Revoke affected keys, isolate impacted tenant workflows, and pause automated actions when needed.
3

Recover

Replay events safely from logs/exports and validate data consistency across downstream systems.
4

Review

Document root cause, corrective actions, and any policy updates required for recurrence prevention.
Enterprise customers can request security and architecture review artifacts through the standard support and security review process.