Connect KoeIQ to your contact centre stack

Direct integration with Advanced Media's AmiVoice API — the leading Japanese speech recognition engine. Used for both batch transcription and live browser streaming.

Native Kintone integration automatically creates records in your Kintone workspace when a call is analyzed — including quality score, agent, intent classification, summary, and a link to the transcript. No webhook configuration required.

Built on AWS Tokyo (ap-northeast-1). S3 for audio storage, SQS for job queuing, ECS for compute, RDS for Postgres, and Secrets Manager for credential management.

Auto-ingest recorded calls from Amazon Connect via S3 event triggers or webhook. No manual upload required — calls flow directly into the KoeIQ pipeline.

Native Salesforce integration uses OAuth 2.0 client credentials to push each completed call as a Task activity (or custom object) — no user login or middleware required. Includes quality score, intent, summary, and transcript link.

Receive call completion events from Genesys Cloud via EventBridge or webhook. Route recordings directly to the ingest API for automated processing.

Use KoeIQ's REST API via Zapier or Make (formerly Integromat) to connect to 5,000+ apps without writing code. Trigger on new calls, scores, or keyword hits.

S3 object-creation event triggers automatic ingest. Ideal for Amazon Connect, Genesys Cloud, and any CCaaS that writes recordings to S3.

Push recording files to the KoeIQ SFTP endpoint. Works with on-premises PBX and legacy CC systems — scheduled batch or real-time push.

HTTP POST a multipart audio file with an X-API-Key header. Best for custom CTI middleware and programmatic ingest from in-house systems.

Receive call-completion webhooks, fetch the recording URL, and automatically feed the pipeline. Pairs with CRMs and call-management platforms.

REST API

Full API access to every feature

Upload calls, trigger analytics, retrieve results, and manage users — all via REST API. API keys are issued instantly from the app settings page.

• ✓API key authentication (instant from settings)
• ✓Bearer token auth (JWT) for user-scoped calls
• ✓OpenAPI 3.0 spec for all endpoints
• ✓Rate limit: 100 req/min default (configurable)
• ✓Consistent JSON error responses

Example Webhook Payload

{
  "event": "call.analyzed",
  "call_id": "c_01J...",
  "timestamp": "2026-03-12T09:15:00Z",
  "tenant_id": "t_abc...",
  "data": {
    "quality_score": 87,
    "emotion": "neutral",
    "intent": "complaint_handling",
    "summary": "Customer enquired about claim status...",
    "keywords_matched": ["complaint", "claim delay"]
  }
}

All webhooks are HMAC-SHA256 signed. Verify via X-KoeIQ-Signature header.