Kajabi
Kajabi is an all-in-one creator platform that enables entrepreneurs and knowledge creators to build, market, and sell digital products including online courses, membership sites, coaching programs, and communities. The Kajabi Public API provides a RESTful interface for managing contacts, products, offers, purchases, orders, transactions, forms, webhooks, and more. API access requires OAuth 2.0 authentication and is available exclusively on the Pro plan. The API base URL is https://api.kajabi.com with versioned endpoints under /v1, and an OpenAPI specification is published in the public_api_docs GitHub repository.
Real signal across most facets with visible, nameable gaps — the contract exists but is thin, or the portal is good while governance and commercial terms are absent.
API Evangelist profiles Kajabi the way a machine reads it — 58 machine-readable artifacts across 21 APIs, pulled from the provider's own public surface and indexed so a developer, an analyst, or an AI agent can evaluate it against every other provider on the network.
Every provider in the network is reduced to the same set of machine-readable artifacts — OpenAPI contracts, event specifications, GraphQL schemas, runnable collections, pricing and rate-limit signals, security posture, OAuth scopes, and the agent surfaces (MCP servers and skills) that let software drive the API on its own. We profile them because the interface is the part of a company you can actually inspect: it is a truer signal of what a provider does than any marketing page. From those artifacts we compute the Kin Score — Kajabi scores 51.1/100 (developing), with a separate agent-readiness read of 48/100 (agent ready). The full breakdown is below, followed by every artifact we hold — each card links through to its machine-readable definition on apis.io.
Kin Score
This is the API Evangelist rating — a single, repeatable read computed from the artifacts on this page. Green fill is points earned; the red track is points possible, so every bar shows earned-versus-possible at a glance.
Kin Score
How this is scored →scored 2026-07-27 · rubric v0.5
How we profile Kajabi
Each block below is one kind of artifact we hold for Kajabi. For each we say what it is and why it earns a place in the profile, then list every one we've indexed — capped at two rows, scroll within the panel for the rest.
APIs 21
Each API is captured as its own OpenAPI definition — every operation, parameter, and response. This is the single most useful machine-readable description of what an API does, and it's what lets us score, lint, mock, and generate against it without asking the provider for anything.
Individual APIs this provider publishes, each with its own machine-readable definition.
Kajabi Authentication API
The Authentication API from Kajabi — 2 operation(s) for authentication.
Kajabi Blog posts API
The Blog posts API from Kajabi — 2 operation(s) for blog posts.
Kajabi Contact Notes API
The Contact Notes API from Kajabi — 2 operation(s) for contact notes.
Kajabi Contact Tags API
The Contact Tags API from Kajabi — 2 operation(s) for contact tags.
Kajabi Contacts API
The Contacts API from Kajabi — 4 operation(s) for contacts.
Kajabi Courses API
The Courses API from Kajabi — 2 operation(s) for courses.
Kajabi Custom Fields API
The Custom Fields API from Kajabi — 2 operation(s) for custom fields.
Kajabi Customers API
The Customers API from Kajabi — 3 operation(s) for customers.
Kajabi Forms API
The Forms API from Kajabi — 5 operation(s) for forms.
Kajabi Kajabi Payments Payouts API
The Kajabi Payments Payouts API from Kajabi — 2 operation(s) for kajabi payments payouts.
Kajabi Landing pages API
The Landing pages API from Kajabi — 2 operation(s) for landing pages.
Kajabi Me API
The Me API from Kajabi — 1 operation(s) for me.
Kajabi Offers API
The Offers API from Kajabi — 3 operation(s) for offers.
Kajabi Orders API
The Orders API from Kajabi — 4 operation(s) for orders.
Kajabi Podcasts API
The Podcasts API from Kajabi — 2 operation(s) for podcasts.
Kajabi Products API
The Products API from Kajabi — 2 operation(s) for products.
Kajabi Purchases API
The Purchases API from Kajabi — 5 operation(s) for purchases.
Kajabi Sites API
The Sites API from Kajabi — 4 operation(s) for sites.
Kajabi Transactions API
The Transactions API from Kajabi — 2 operation(s) for transactions.
Kajabi Version API
The Version API from Kajabi — 1 operation(s) for version.
Kajabi Webhooks API
The Webhooks API from Kajabi — 8 operation(s) for webhooks.
Scroll within the panel for all 21 ·
GraphQL 1
Where a provider ships GraphQL, the schema is the contract. We profile it alongside the REST surface so the whole interface is legible in one place.
GraphQL schemas published by this provider.
Kajabi GraphQL Schema
This document describes a conceptual GraphQL schema for the Kajabi creator and online course platform. Kajabi's public API is RESTful (base URL: `https://api.kajabi.com/v1`, OAu...
GRAPHQLPricing Plans 1
Pricing is part of the interface. Machine-readable plans tell you what a tier costs and includes before you commit — one of the six things the Kin Score reads for commercial clarity.
Published pricing tiers and plan structures.
Kajabi Plans Pricing
PLANSRate Limits 1
Rate limits are the difference between a demo that works and a production integration that doesn't fall over. Publishing them is an operational-transparency signal — and a hard requirement for any agent that plans its own throughput.
Documented rate limits and quota policies.
Kajabi Rate Limits
RATE LIMITSFinOps 1
Cost, billing, and metering signals let a buyer model the financial operations of an API before it's live. We profile them for the same reason we profile pricing: the money is part of the contract.
Cost, billing, and metering signals for API financial operations.
Kajabi Finops
FINOPSSemantic Vocabularies 1
JSON-LD contexts give the data shared meaning across APIs. We profile them because semantics are what let a machine reconcile 'customer' here with 'customer' somewhere else.
JSON-LD contexts and semantic vocabularies used across these APIs.
Kajabi Context
JSON-LDSpectral Rules 1
Governance rulesets we run against this provider's specs — the automated checks behind parts of the score. Profiling them makes the quality bar explicit and re-runnable, not a matter of opinion.
Kajabi API Rules
SPECTRALJSON Schema 20
Standalone JSON Schema definitions describe the data models behind the API. We profile them so the shapes are validatable on their own — useful long after a single request is forgotten.
Standalone JSON Schema definitions for this provider's data models.
Blog Posts
JSON SCHEMAContact Notes
JSON SCHEMAContact Tags
JSON SCHEMAContacts
JSON SCHEMACourses
JSON SCHEMACustom Fields
JSON SCHEMACustomers
JSON SCHEMAForm
JSON SCHEMAForm Submission
JSON SCHEMAHooks
JSON SCHEMALanding Pages
JSON SCHEMAMe
JSON SCHEMAOffers
JSON SCHEMAOrders
JSON SCHEMAPodcasts
JSON SCHEMAProducts
JSON SCHEMAPurchases
JSON SCHEMASites
JSON SCHEMATransactions
JSON SCHEMAWebsite Pages
JSON SCHEMAScroll within the panel for all 20 ·
Examples 8
Real request and response payloads are what turn a spec from abstract into obvious — and they're one of the twelve things an agent needs to call an API correctly on the first try.
Example request and response payloads for these APIs.
Kajabi Contacts List Example
EXAMPLEKajabi Offers List Example
EXAMPLEKajabi Orders List Example
EXAMPLEKajabi Products List Example
EXAMPLEKajabi Webhooks List Example
EXAMPLEScroll within the panel for all 8 ·
Security Posture 2
Authentication, domain security, vulnerability disclosure, and trust-center signals — the evidence that a provider takes security seriously enough to document it. We profile it because you can't govern what you can't see.
Authentication, domain security, vulnerability disclosure, and trust-center signals.
Agentic Access 1
An x-agentic-access contract marks which operations are safe for an agent to run on its own and which need a human in the loop. It is the difference between an API an agent can use and one it can use safely.
Recommended x-agentic-access execution contracts for AI agents.
Resources
Every other property we hold for Kajabi — documentation, portals, status pages, policies, and corporate surface — grouped by the job it does, following the integrator's arc from getting started to running in production.
Documentation 1
Reference material describing how the API behaves
Agent Surfaces 1
MCP servers, agent skills, and machine-readable catalogs
Build 1
SDKs, sample code, and the tooling you integrate with
Access & Security 2
Authentication, authorization, and security posture
Operate 2
Status, limits, changes, and where to get help
Commercial 3
Pricing, plans, and the legal terms of use
Company 3
The organization behind the API
Other 1
Properties that don't map to a standard resource type
← All providers · Data indexed from github.com/api-evangelist/kajabi · machine-readable index on apis.io