# Kixie

> Kixie is a sales-engagement and revenue-communications platform built around PowerCall — a
> multi-line power dialer, business phone service and SMS/MMS product that integrates
> bi-directionally with HubSpot, Salesforce, Pipedrive, Zoho and GoHighLevel. Its public API is a
> small, event-oriented HTTP surface served from the apig.kixie.com gateway.

This file is generated by API Evangelist from Kixie's public developer documentation. Kixie does
not publish an llms.txt of its own (https://www.kixie.com/llms.txt and
https://developer.kixie.com/llms.txt both returned 404 on 2026-08-12), and publishes no OpenAPI,
AsyncAPI or GraphQL contract. Everything below was read from human-readable documentation.

## What an agent needs to know first

- **Authentication** is a single account-scoped API key (`apikey`) plus a numeric Business ID
  (`businessid`). One key per account, not per user. The key goes in BOTH the query string and
  the JSON body on the Event API. The Agent Status API uses `apiKey` (camel-case) instead.
- **The key must be activated by Kixie Support** before first use, and requires a paid account
  with at least one Professional-tier agent. There is no self-service API onboarding.
- **Rate limit**: 10,000 API calls per account per day, resetting at 00:00 UTC. No rate-limit
  response headers are returned, so there is no runtime signal for remaining budget.
- **There is no idempotency key.** Every primary operation places a call or sends a message.
  Do not auto-retry on timeout — you will double-dial or double-text a real person.
- **There are no read APIs.** Apart from agent presence, everything is a write or a webhook.
  You cannot list PowerLists, fetch a call record, or read a contact back out over HTTP.
- **Error semantics are undocumented.** Kixie publishes no error catalogue, no status-code
  reference, and no error response example for any Event API operation.

## API surface

Base: `https://apig.kixie.com`

### Event API — POST /app/event
One endpoint that dispatches on an `eventname` string in the JSON body, with a secondary `action`
discriminator on some families.

- `eventname: call` — place an outbound call (rings the agent at `email`, then dials `target`)
- `eventname: sms` — send an SMS from the agent's number
- `eventname: bizsms` — send a Team/Business SMS from a shared number (requires Team SMS `id`)
- `eventname: queue` — send a call to an inbound queue (`action: remove` to remove)
- `eventname: cadence` — add to an automation cadence (`action: remove` to remove)
- `eventname: updatepowerlist` — add or update a PowerList contact, keyed on phone number
- `eventname: removefrompowerlist` — remove from one PowerList (`action: removefrompowerlist`)
  or from every PowerList (`action: removefromallpowerlists`)

Legacy: POST /app/legacy/flushUserQueue (`call: flushUserQueue`) drops every queued call.

### Webhook Management API — POST /app/v1/api/*
Dispatches on a `call` field, not on HTTP verbs. Reads and deletes are both POST.

- `/postwebhook` with `call: postWebhook` — create
- `/postwebhook` with `call: putWebhook` — update
- `/getWebhooks` with `call: getWebhooks` — list all
- `/deleteWebhooks` with `call: removeWebhook` — delete by `webhookid`

### Agent Status API — GET /www/agent/status?apiKey=…&email=…
Returns `{success, result: {onCall, registered, device}}`. Booleans arrive as 0/1 integers.
A `false` success means the agent is offline — a business outcome, not an error.

## Events (webhooks)

Kixie posts JSON to endpoints you register. All payloads are wrapped in a top-level `data` object;
call-bearing events nest the record under `data.callDetails`.

- `endcall` — call ended, with duration, cost, disposition, recording URL
- `startcall` — call started
- `answeredcall` — call answered
- `voicemail` — voicemail left
- `disposition` — agent recorded a call outcome
- `sms` — SMS sent or received, with resolved CRM contact
- `scheduledactivity` — follow-up scheduled from a call
- `cisummary` — AI call summary, sentiment, keyword/phrase hits (Conversation Intelligence add-on)
- `powerdialattempt` — number dialled but not connected during a PowerList session

**Webhook deliveries are not signed.** No HMAC, no timestamp header, no replay protection. The
only control is an optional static custom header set at registration. No retry policy or
redelivery endpoint is published.

Kixie also calls INTO customer-implemented endpoints for its Custom CRM integration: a GET Contact
Lookup (E.164 number as a `number` query parameter, returning a snake_case contact object), plus
POST endpoints for dispositions, contact edits and scheduled activities.

## Documentation

- Developer portal: https://developer.kixie.com/
- Authentication overview: https://support.kixie.com/hc/en-us/articles/7273987300635-Kixie-Authentication-Overview
- PowerList API (also the only place the rate limit is published): https://support.kixie.com/hc/en-us/articles/19135310564635-PowerList-API
- Business/Team SMS API: https://support.kixie.com/hc/en-us/articles/19171653389339-Business-Team-SMS-API
- Make a Call API: https://support.kixie.com/hc/en-us/articles/19177004217243-Make-a-Call-API
- Send to Queue API: https://support.kixie.com/hc/en-us/articles/19199139766683-Send-to-Queue-API
- Agent Status API: https://support.kixie.com/hc/en-us/articles/360020051474-Kixie-Agent-Status-API
- Managing webhooks via API: https://support.kixie.com/hc/en-us/articles/20871662051739-Managing-Kixie-Event-Webhooks-via-API
- Help center: https://support.kixie.com/hc/en-us
- Status page (open JSON API): https://status.kixie.com/api/v2/summary.json
- Security and disclosure: https://www.kixie.com/security/ — security@kixie.com
- Pricing: https://www.kixie.com/pricing/
- Sign up: https://www.kixie.com/sign-up/
- Postman workspace: https://www.postman.com/kixie-sales/kixie-public/
- GitHub: https://github.com/Kixie-com

## What Kixie does not publish

- No OpenAPI, Swagger, AsyncAPI, GraphQL SDL or JSON Schema anywhere.
- No client SDK in any package registry (npm, PyPI, RubyGems, NuGet, crates.io, Packagist all
  returned zero first-party packages on 2026-08-12).
- No CLI.
- No MCP server (mcp.kixie.com returns 404).
- No A2A agent card at /.well-known/agent-card.json or /.well-known/agent.json on any host.
- No /.well-known/security.txt, openid-configuration, oauth-authorization-server or api-catalog.
- No error-code reference. No idempotency support. No rate-limit response headers.
- No OAuth 2.0, no scopes, no per-user credentials.
- No deprecation policy, no Sunset headers, no SLA, no public roadmap.
- No published prices for any of its three subscription tiers.
- No compliance certifications — stated deliberately: the security page "intentionally does not
  claim a certification, audit result, hosting architecture, retention period, or control that has
  not been confirmed for publication."

## Note on the WordPress hosts

www.kixie.com and developer.kixie.com run WordPress with fuzzy-match URL redirection. Any unknown
path returns 301 to a loosely-similar marketing page rather than 404 — /.well-known/agent-card.json
redirects to /integrations/agentforce-marketing/, and /roadmap/ redirects to /integrations/monday/.
A crawler that follows redirects and records the final 200 will falsely credit Kixie with
documents it does not serve. Verify the body, not the status code.

---
generated: 2026-08-12
method: generated
source: apis.yml + developer.kixie.com + support.kixie.com (Kixie publishes no llms.txt)