echowin API

Name: echowin API
Brand: echowin API
Availability: InStock

✓ Official Vendor SpecCommunicationsVoice TelephonyapiKey33 EndpointsREST

For Agents

Manage echowin AI phone agents, read call records and contacts, update agent instructions, and run knowledgebase and board automations through 33 REST endpoints.

Install Jentic One Beta

Connect the echowin API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the echowin API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.

Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.

Step 1: Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
jentic register       # connects your agent to your Jentic One instance

Jentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.

Capabilities

What an agent can do with echowin API.

List and update AI agent instructions that drive how echowin handles inbound calls

Sync contacts and contact notes between echowin and an external CRM

Read call records to extract transcripts and outcomes for analysis

GET STARTED

Start building with echowin API

Explore with Jentic

View OpenAPI Document

Use Cases

Patterns agents use echowin API for, with concrete tasks.

★ AI Receptionist for Small Businesses

Small businesses use echowin as an AI receptionist that answers calls, captures lead details, and books follow-ups. The API lets the business read call records, update agent instructions when offerings change, and sync contacts back into their CRM. The endpoint surface covers agents, contacts, calls, and notes so the entire call lifecycle stays in sync without manual data entry.

List recent calls for an agent, push each caller's contact and notes into the business CRM, and tag qualified leads.

CRM Contact and Note Sync

Businesses already running a CRM want call activity to flow into customer records automatically. The echowin API exposes /api/v1/contacts for create, list, and update, plus /api/v1/contacts/{contactId}/notes for per-call notes. A nightly or webhook-driven sync keeps the CRM contact record up to date with what the AI agent learned during recent calls.

On call completion, GET the new echowin contact, POST a contact note containing the call summary, then push both into the destination CRM.

Knowledgebase and Agent Instruction Management

When pricing, hours, or product details change, the AI agent's grounding must update too. The echowin API exposes knowledgebase endpoints and PUT /api/v1/agents/{agentId}/instructions so an admin tool or CI pipeline can push changes from a single source of truth. The agent then handles new calls with the updated context immediately.

PUT /api/v1/agents/{agentId}/instructions with new instructions reflecting the latest pricing and confirm the change took effect.

Post-Call Task Routing via Boards

echowin's board resource works like a kanban that organises post-call follow-ups. Using the contacts assignments endpoints and board endpoints, an integration can move a contact to the right board column when the AI agent flags an issue. This replaces manual triage and keeps the team focused on calls that need a human.

When a call ends with a 'needs callback' tag, list the contact's assignments and create a new board card on the callbacks column.

AI Agent Voice Workflow Orchestration

An external AI agent can use Jentic to discover echowin operations and coordinate a multi-step voice workflow - list calls, read transcripts, summarise, update CRM contacts, and adjust knowledgebase entries - without an engineer wiring those calls. Jentic delivers the X-API-Key auth and operation schemas into the agent's context for each step.

Through Jentic, search 'list echowin calls and update contact notes', load the relevant schemas, and execute the call-to-CRM update flow.

Key Endpoints

33 endpoints — echowin is an ai-powered phone answering platform that handles inbound calls with virtual agents and routes follow-up actions back to a business.

METHOD

PATH

DESCRIPTION

GET

/api/v1/agents

List all AI agents

PUT

/api/v1/agents/{agentId}/instructions

Update agent instructions

GET

/api/v1/contacts

List contacts

POST

/api/v1/contacts

Create a contact

POST

/api/v1/contacts/bulk

Bulk-create contacts

POST

/api/v1/contacts/{contactId}/notes

Create a note for a contact

GET

/api/v1/agents

List all AI agents

PUT

/api/v1/agents/{agentId}/instructions

Update agent instructions

GET

/api/v1/contacts

List contacts

POST

/api/v1/contacts

Create a contact

POST

/api/v1/contacts/bulk

Bulk-create contacts

POST

Why Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

Your echowin X-API-Key is stored once, encrypted, by your own Jentic One instance and injected as the request header at execution time. It never enters the agent's prompt, logs, or context.

Intent-based discovery

Agents search Jentic by intent such as 'list echowin calls' or 'update an echowin agent's instructions', and Jentic returns the matching operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

Time to first call

FAQs

Specific to using echowin API through Jentic.

What authentication does the echowin API use?

The echowin API uses an API key passed in the X-API-Key request header (the apiKey scheme). Through Jentic, the key is stored encrypted in your Jentic One instance and is injected into the X-API-Key header at call time so it never enters the agent's context.

Can I update an echowin AI agent's instructions through the API?

Yes. PUT /api/v1/agents/{agentId}/instructions accepts the new instruction text and applies it so subsequent inbound calls run with the updated guidance.

What are the rate limits for the echowin API?

The OpenAPI spec does not publish per-endpoint rate limits. echowin applies fair-use limits per workspace; bulk endpoints such as POST /api/v1/contacts/bulk help reduce request volume when importing many records.

How do I sync echowin call notes to my CRM through Jentic?

Search 'list echowin contacts and notes' in Jentic, load the GET /api/v1/contacts and GET /api/v1/contacts/{contactId}/notes schemas, and chain the calls. Jentic handles the X-API-Key header and returns the contact-plus-notes payload to forward into your CRM.

Does the echowin API expose call recordings or transcripts?

The Calls resource exposes call records and metadata. Recording or transcript availability depends on the workspace plan and is returned as part of the call resource fields when present.

Can I limit what my agent is allowed to do with the echowin API?

Yes. Jentic One is self-hosted by you, so your own rules decide which echowin operations and credentials the agent may use. Because echowin puts the resource id in the URL path, such as /agents/{agentId}/instructions and /contacts/{contactId}/notes, you can pin the agent to a single phone agent or a single contact. You choose which operations it may call, so you can allow reading agents and adding contact notes while keeping bulk contact creation via POST /api/v1/contacts/bulk off unless you add it.

echowin API

Connect the echowin API to your agent

Capabilities

Start building with echowin API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs