Complete SDK implementations for Interactor platform integration. Use when building TypeScript/Node.js or Python applications that need full Interactor client libraries. Includes complete client classes, webhook handlers, SSE streaming, and production-ready patterns.
Production-ready SDK implementations for TypeScript/Node.js and Python with complete client classes, webhook handlers, and real-time streaming components.
interactor-auth skill (OAuth client credentials)axios, @types/nodehttpx (for async client), requests (for sync client)# Required - from interactor-auth setup
INTERACTOR_CLIENT_ID=client_xxx
INTERACTOR_CLIENT_SECRET=secret_xxx
# Optional - webhook secret for signature verification
INTERACTOR_WEBHOOK_SECRET=whsec_xxx
┌─────────────────────────────────────────────────────────────────────┐
│ YOUR APPLICATION │
│ │
│ Your Users ──────> Your Backend ──────> INTERACTOR │
│ (you manage auth) (client_credentials) (platform APIs) │
│ (namespaces per user) │
└─────────────────────────────────────────────────────────────────────┘
| Service | URL | Purpose |
|---|---|---|
| Account Server | https://auth.interactor.com/api/v1 | Authentication, OAuth clients |
| Core API | https://core.interactor.com/api/v1 | Credentials, Agents, Workflows |
Namespaces provide multi-tenant isolation. Each namespace represents a distinct user or tenant in your application.
| Pattern | Example | Use Case |
|---|---|---|
| User-based | user_12345 | Per-user credential storage |
| Organization-based | org_acme_corp | Team/company isolation |
| Composite | org_acme_user_123 | User within organization |
Namespaces can be passed in two ways (both are supported):
// Method 1: X-Namespace header (recommended for all endpoints)