Kixie

Kixie is a Los Angeles based sales-engagement and revenue-communications platform built around PowerCall, a multi-line power dialer, business phone service and SMS/MMS product that plugs bi-directionally into HubSpot, Salesforce, Pipedrive, Zoho and GoHighLevel. Its public developer surface is a small, event-oriented HTTP API served from the apig.kixie.com gateway: a single POST /app/event endpoint that dispatches on an eventname discriminator to place calls, send SMS and Team SMS, add and remove contacts from PowerLists, push numbers into and out of calling queues and cadences; a webhook management API for creating, listing, updating and deleting the eight documented event webhooks; and an agent-status lookup. Authentication is a single account scoped API key plus a Business ID, and the platform publishes a documented daily usage cap of 10,000 API calls per account. Kixie publishes no OpenAPI, AsyncAPI or GraphQL contract and ships no first-party client SDKs; the reference is human-readable HTML on developer.kixie.com and in the Zendesk help center.

Kixie publishes 3 APIs on the APIs.io network. Tagged areas include Company, Sales Engagement, Voice, Telephony, and SMS.

The Kixie catalog on APIs.io includes 1 event-driven AsyncAPI specification.

Kixie’s developer surface includes documentation, API reference, getting-started guide, support, engineering blog, pricing, signup flow, and 25 more developer resources.

59.0/100 strong ▬ flat Agent 34/100 agent aware Full breakdown ↓
scored 2026-08-17 · rubric v0.11.0
3 APIs
CompanySales EngagementVoiceTelephonySMSMessagingContact CenterPower DialerCRMWebhooksCommunicationsRevenue Operations

Kin Score

Kin Score Kin Score How this is scored →
scored 2026-08-17 · rubric v0.11.0
Composite quality — 59.0/100 · strong
Contract Quality 11.0 / 21
Developer Ergonomics 9.6 / 17
Commercial Clarity 14.3 / 17
Operational Transparency 8.4 / 11
Governance 1.3 / 10
Discoverability 6.9 / 9
Regulatory Posture 7.5 / 15
Agent readiness — 34/100 · agent aware
Machine-Readable Contract 18 / 18
Agentic Access Contract 0 / 10
MCP Server 0 / 12
Machine-Readable Auth 10 / 10
Idempotency 0 / 9
Stable Error Semantics 0 / 8
Request/Response Examples 0 / 7
Rate-Limit Signaling 7 / 7
Typed Event Surface 6 / 6
Agent Skills 0 / 5
Well-Known Catalog 0 / 4
Consent & Bot Identity 0 / 3
A2A Agent Card 0 / 8
Dry-Run / Simulate Mode 0 / 4
Regulatory Posture applies to this provider. Its tags matched the Telecommunications regime, so Regulatory Posture carries 15 points of the composite. If this regime is wrong for your business, say so on your provider repo — the applicability map is public and we will correct it.
The six quality facets above are damped to 85 points between them, because the conditional facet above carries the other 15. That is why each facet's contribution is shown against a damped maximum: raising a quality facet moves the composite by 85% of its nominal weight, not 100%. The full arithmetic is at apis.io/rating/.
Improve this rating by publishing the missing artifacts — every area above can be raised, and the full rubric is at apis.io/rating/. This rating is computed from github.com/api-evangelist/kixie: open an issue to ask a question, or submit a pull request to add artifacts. Want it done for you? Prioritized profiling — $2,500 →

APIs 3

Individual APIs this provider publishes, each with its own machine-readable definition.

Kixie Event API

The primary Kixie automation surface. A single POST endpoint on the apig.kixie.com gateway that dispatches on an `eventname` discriminator in the JSON body — `call` (place an ou...

Kixie Webhook Management API

A path-versioned management surface for Kixie's event webhooks. Four POST operations — postWebhook (create), putWebhook (update), getWebhooks (list) and removeWebhook (delete) —...

Kixie Agent Status API

A read-only lookup that returns the current presence of a Kixie agent by email address — whether the agent's device is registered (logged in) and whether the agent is currently ...

Pricing Plans 1

Published pricing tiers and plan structures.

Kixie Plans Pricing

3 plans

PLANS

Rate Limits 1

Documented rate limits and quota policies.

Kixie Rate Limits

1 limits

RATE LIMITS

Event Specifications 1

AsyncAPI definitions for this provider's event-driven and streaming APIs.

Kixie Webhooks

ASYNCAPI

Security Posture 4

Authentication, domain security, vulnerability disclosure, and trust-center signals.

Kixie Authentication

4 schemes

SECURITY

Kixie Domain Security

TLSv1.3 · DMARC

SECURITY

Kixie Vulnerability Disclosure

contact published

SECURITY

Kixie Trust Center

trust center published

SECURITY

Resources

Get Started 4

Portal, sign-up, and the first successful call

Documentation 2

Reference material describing how the API behaves

Agent Surfaces 1

MCP servers, agent skills, and machine-readable catalogs

Design & Contract 5

Pagination, idempotency, versioning, errors, and events

Build 3

SDKs, sample code, and the tooling you integrate with

Access & Security 5

Authentication, authorization, and security posture

Operate 5

Status, limits, changes, and where to get help

Commercial 4

Pricing, plans, and the legal terms of use

Company 3

The organization behind the API

Source (apis.yml)

apis.yml Raw ↑
aid: kixie
name: Kixie
description: 'Kixie is a Los Angeles based sales-engagement and revenue-communications platform built around PowerCall, a
  multi-line power dialer, business phone service and SMS/MMS product that plugs bi-directionally into HubSpot, Salesforce,
  Pipedrive, Zoho and GoHighLevel. Its public developer surface is a small, event-oriented HTTP API served from the apig.kixie.com
  gateway: a single POST /app/event endpoint that dispatches on an eventname discriminator to place calls, send SMS and Team
  SMS, add and remove contacts from PowerLists, push numbers into and out of calling queues and cadences; a webhook management
  API for creating, listing, updating and deleting the eight documented event webhooks; and an agent-status lookup. Authentication
  is a single account scoped API key plus a Business ID, and the platform publishes a documented daily usage cap of 10,000
  API calls per account. Kixie publishes no OpenAPI, AsyncAPI or GraphQL contract and ships no first-party client SDKs; the
  reference is human-readable HTML on developer.kixie.com and in the Zendesk help center.'
url: https://raw.githubusercontent.com/api-evangelist/kixie/refs/heads/main/apis.yml
image: https://www.kixie.com/wp-content/uploads/2026/02/Kixie-Logo-Light.png
x-type: company
x-source: harvest:marketing-integration-graph
specificationVersion: '0.20'
created: '2026-08-12'
modified: '2026-08-12'
tags:
- Company
- Sales Engagement
- Voice
- Telephony
- SMS
- Messaging
- Contact Center
- Power Dialer
- CRM
- Webhooks
- Communications
- Revenue Operations
apis:
- aid: kixie:kixie-event-api
  name: Kixie Event API
  description: The primary Kixie automation surface. A single POST endpoint on the apig.kixie.com gateway that dispatches
    on an `eventname` discriminator in the JSON body — `call` (place an outbound call through an agent), `sms` (send an SMS
    from an agent number), `bizsms` (send a Team/Business SMS), `queue` (send a call to, or remove it from, an inbound queue),
    `cadence` (add to or remove from an automation cadence), `updatepowerlist` (add or update a PowerList contact) and `removefrompowerlist`
    (remove from one or all PowerLists). Authenticated with an account API key passed both as a query parameter and in the
    body, alongside the account Business ID.
  humanURL: https://developer.kixie.com/
  baseURL: https://apig.kixie.com/app/event
  tags:
  - Voice
  - SMS
  - Power Dialer
  - Automation
  properties:
  - type: Documentation
    url: https://developer.kixie.com/
  - type: APIReference
    url: https://developer.kixie.com/
  - type: Authentication
    url: authentication/kixie-authentication.yml
  - type: RateLimits
    url: rate-limits/kixie-rate-limits.yml
  - type: Conventions
    url: conventions/kixie-conventions.yml
  - type: DataModel
    url: data-model/kixie-data-model.yml
- aid: kixie:kixie-webhook-management-api
  name: Kixie Webhook Management API
  description: A path-versioned management surface for Kixie's event webhooks. Four POST operations — postWebhook (create),
    putWebhook (update), getWebhooks (list) and removeWebhook (delete) — register HTTP callbacks for the eight documented
    event types (endcall, startcall, answeredcall, SMS, disposition, voicemail, scheduledactivity, cisummary), with optional
    direction, call-result and disposition filters and optional custom request headers.
  humanURL: https://support.kixie.com/hc/en-us/articles/20871662051739-Managing-Kixie-Event-Webhooks-via-API
  baseURL: https://apig.kixie.com/app/v1/api
  tags:
  - Webhooks
  - Events
  - Management
  properties:
  - type: Documentation
    url: https://support.kixie.com/hc/en-us/articles/20871662051739-Managing-Kixie-Event-Webhooks-via-API
  - type: Webhooks
    url: asyncapi/kixie-webhooks.yml
  - type: Authentication
    url: authentication/kixie-authentication.yml
- aid: kixie:kixie-agent-status-api
  name: Kixie Agent Status API
  description: A read-only lookup that returns the current presence of a Kixie agent by email address — whether the agent's
    device is registered (logged in) and whether the agent is currently on a call — wrapped in a `success` / `result` envelope.
    Authenticated with the account API key as an `apiKey` query parameter.
  humanURL: https://support.kixie.com/hc/en-us/articles/360020051474-Kixie-Agent-Status-API
  baseURL: https://apig.kixie.com/www/agent/status
  tags:
  - Presence
  - Agents
  - Contact Center
  properties:
  - type: Documentation
    url: https://support.kixie.com/hc/en-us/articles/360020051474-Kixie-Agent-Status-API
  - type: Authentication
    url: authentication/kixie-authentication.yml
maintainers:
- FN: Kin Lane
  email: kin@apievangelist.com
- FN: APIs.json
  email: info@apis.io
common:
- type: Website
  url: https://www.kixie.com/
- type: DeveloperPortal
  url: https://developer.kixie.com/
- type: Documentation
  url: https://developer.kixie.com/
- type: APIReference
  url: https://developer.kixie.com/
- type: GettingStarted
  url: https://support.kixie.com/hc/en-us/articles/7273987300635-Kixie-Authentication-Overview
- type: Support
  url: https://support.kixie.com/hc/en-us
- type: HelpCenter
  url: https://support.kixie.com/hc/en-us
- type: Blog
  url: https://www.kixie.com/sales-blog/
- type: BlogRSS
  url: https://www.kixie.com/sales-blog/feed/
- type: GitHubOrganization
  url: https://github.com/Kixie-com
- type: Pricing
  url: https://www.kixie.com/pricing/
- type: SignUp
  url: https://www.kixie.com/sign-up/
- type: Login
  url: https://app.kixie.com/
- type: TermsOfService
  url: https://www.kixie.com/terms/
- type: PrivacyPolicy
  url: https://www.kixie.com/privacy/
- type: Postman
  url: https://www.postman.com/kixie-sales/kixie-public/
- type: Integrations
  url: https://www.kixie.com/integrations/
- type: StatusPage
  url: https://status.kixie.com/
- type: Lifecycle
  url: lifecycle/kixie-lifecycle.yml
- type: ChangeLog
  url: changelog/kixie-changelog.yml
- type: Authentication
  url: authentication/kixie-authentication.yml
- type: Conventions
  url: conventions/kixie-conventions.yml
- type: RateLimits
  url: rate-limits/kixie-rate-limits.yml
- type: Plans
  url: plans/kixie-plans-pricing.yml
- type: Webhooks
  url: asyncapi/kixie-webhooks.yml
- type: DataModel
  url: data-model/kixie-data-model.yml
- type: Packages
  url: packages/kixie-packages.yml
- type: Conformance
  url: conformance/kixie-conformance.yml
- type: DomainSecurity
  url: security/kixie-domain-security.yml
- type: VulnerabilityDisclosure
  url: security/kixie-vulnerability-disclosure.yml
- type: Security
  url: security/kixie-vulnerability-disclosure.yml
- type: TrustCenter
  url: security/kixie-trust-center.yml
- type: LLMsTxt
  url: llms/kixie-llms.txt
x-vouched-by:
- Nutshell
- Vendasta
x-vouch-count: 2
x-enrichment:
  date: '2026-08-12'
  status: enriched
  artifacts_added: 16
  pass: local-v1
x-coverage:
  state: covered
  reason: no-machine-readable-spec
  detail: Kixie's developer reference is public, server-rendered and fully readable — three API surfaces and nine webhook
    payloads were harvested from developer.kixie.com and the open Zendesk Help Center API — but Kixie publishes no OpenAPI,
    AsyncAPI, GraphQL SDL or JSON Schema anywhere, so every contract artifact in this repo is transcribed from prose rather
    than parsed.
  evidence:
  - url: https://developer.kixie.com/
    status: 200
  - url: https://apig.kixie.com/openapi.json
    status: 403
  - url: https://developer.kixie.com/openapi.json
    status: 301
  - url: https://support.kixie.com/api/v2/help_center/en-us/sections/360008032094/articles.json
    status: 200
  checked: '2026-08-12'