What we do
Tools
Industries
Department
How we workLet's talk →
Home/Keap/Where the Keap API Documentation Lives Now
Keap developer docs

Keap API Documentation: The REST v2 Reference, the v1 Reference and the Old XML-RPC Pages

Search for Keap's API docs and the results come from three eras: Infusionsoft's XML-RPC API, REST v1 and REST v2. All three are still listed on developer.keap.com. Keap's own quickstarts use v2, so that's the reference for new work, and the other two matter when you're reading code someone else wrote. Credentials, the end of legacy keys and request quotas are covered on our Keap and the Keap API page.

However you want to go about it
01
Docs home

developer.keap.com, with Getting Started, an OAuth quickstart and a sandbox link.

02
Current reference

Keap Core REST API v2, at api.infusionsoft.com/crm/rest/v2.

03
Still published

Keap Core REST API v1, the XML-RPC API, and a separate Services API.

04
Tools

Postman collections for Core v2, Core v1 and Services, and a PHP SDK for v2.

Which Keap reference to open

Starting fresh: the Keap Core REST API v2 reference. The Getting Started example posts a contact to /crm/rest/v2/contacts.

Maintaining code whose URLs contain /crm/rest/v1/: the Keap Core REST API v1 reference, which still has its own Postman collection.

Code calling methods like ContactService.add or DataService.query: that's the XML-RPC API from the Infusionsoft days, documented under XML-RPC API.

An endpoint on a different base URL: check the Keap Services API, which Keap describes as backend services not proxied through the Core path.

Keap API endpoints grouped around the records you touch

01

Contacts and companies

Create, read and update people and businesses. Custom field values ride on the contact, addressed by the field's numeric ID rather than the label on screen.

02

Tags

Apply or remove tags on contacts. In most Keap accounts a tag is what starts a campaign sequence, so a tag call is often the whole integration.

03

Orders, products and subscriptions

Orders and their items, the product catalog, and recurring subscriptions on a contact.

04

Opportunities

Pipeline deals and the stage each one sits in.

05

Automations

The campaign side of Keap, listed as automations in the v2 docs.

06

REST hooks

Keap's name for webhooks: subscribe a URL to an event such as a new contact or order, and Keap posts to it when that happens, instead of you polling.

REST v1 or REST v2 for a Keap integration

REST v1

/crm/rest/v1/

  • Still documented, with its own Postman collection.
  • What most older integrations and forum answers were written against.
  • The older infusionsoft-php library calls it, and that library is now marked deprecated and no longer maintained.
REST v2

/crm/rest/v2/

  • The version Keap's quickstarts and Getting Started guide use.
  • Covered by Keap's current PHP SDK, keap-sdk-php, which needs PHP 8.3 or later.
  • The place new and changed endpoints show up in the changelog.

Write new work against v2. When moving old v1 code, map each call to its v2 endpoint first, and check the changelog for anything marked deprecated or removed before you rely on it.

SDKs, Postman collections and the Keap changelog

Keap publishes a PHP SDK for v2 on GitHub as keap-sdk-php, and the deprecated infusionsoft-php repository points there, with a migration note for code that used the old library. The docs don't name an official SDK for other languages; instead they show code samples alongside each endpoint, and the Postman collections are the quickest way to try a call with your own token.

The changelog at developer.keap.com/changelog lists entries newest first, each tagged as a new, updated, deprecated or removed endpoint. Read it before an upgrade, and again when a call that worked last month starts returning errors.

The detail that catches people is custom fields. A successful write to the wrong field ID looks exactly like a successful write to the right one, so look up the IDs in your own account and test each field before go-live. n-frames builds Keap integrations on REST v2 this way, with every custom field mapped by ID and checked against a real record.

Reading the Keap API docs

Does Keap have a public API?

Yes. The REST API is documented openly on developer.keap.com, with OAuth for apps other Keap customers install and tokens or keys for your own account. It covers contacts, companies, tags, custom fields, orders, subscriptions, opportunities and automations.

Is the Keap API the same as the old Infusionsoft API?

It's the same platform with newer interfaces. Infusionsoft's XML-RPC API came first and is still documented, then REST v1, then v2. The hostname still says infusionsoft.com. Look at the code's URLs and method names to tell which one it uses.

Do I need a developer to use the Keap API?

To read the docs and make a test call in Postman, no. For anything that runs unattended, such as a REST hook handler, a nightly sync or writes into custom fields, yes: it has to cope with token refresh, quotas, retries and field IDs.

Does Keap's API support webhooks?

Yes, as REST hooks. You subscribe a URL to an event, such as a contact being added or an order being placed, and Keap calls it when that happens, so your system reacts straight away instead of checking on a timer.

Is there an official Keap SDK?

For PHP, yes: keap-sdk-php on Keap's GitHub covers REST v2. The older infusionsoft-php library is deprecated. For other languages the docs give code samples and Postman collections rather than a named SDK.

Let's talk

Tell us the one thing your team does manually that eats up time. We read every message and reply within a day.