Official vendor OpenAPI document · agent-readyCRMContact Managementoauth2281 EndpointsREST
For Agents
Read and write Keap CRM contacts and companies, attach notes and tags, send and record emails, and manage orders. Authenticates with OAuth 2.0 (the oauth2 scheme).
Use for: Create a new contact in Keap for a lead, Update the email address on an existing contact, Add a note to a contact after a call, List the tags applied to a contact
Not supported: Does not handle campaign builder automation, payment gateway configuration, or reporting dashboards. Use for reading and writing contacts, notes, tags, emails, and orders only.
The Keap API is the REST interface to Keap's CRM and sales-and-marketing platform for small businesses. It reads and writes contacts and companies, attaches notes and tags, sends and records emails, and manages orders, so an agent can keep customer records current and act on them. The API covers the core objects a small-business owner tracks day to day, from a new lead through to a paid order. Keap was formerly known as Infusionsoft, which is why its base URL still uses the infusionsoft.com host.
Install Jentic One Beta
Connect the Keap API to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Keap 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.
1
Step 1: Jentic One Host machine
# On the machine that will host your Jentic One instance:
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fkeap.com%2Fkeap" | sh2
Step 2: Agent machine
# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fkeap.com%2Fkeap" | sh
jentic register # connects your agent to your Jentic One instanceJentic 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 Keap API.
Create, read, update, and delete contacts in a Keap account
Attach notes to a contact and read a contact's existing notes
Read the tags applied to a contact for segmentation
Send and record emails against contact records
Create and read orders for a customer
Use Cases
Patterns agents use Keap API for, with concrete tasks.
★ Keep CRM contacts current from an agent
An AI agent can create and update Keap contacts as leads come in from other systems, so the CRM stays current without manual data entry. It creates a contact, updates fields such as email or phone as they change, and reads a contact back to confirm the record. Through Jentic the agent discovers each operation by intent and calls it with the contact details.
Create a Keap contact for a new lead with their name and email, then read the contact back and return its id
Log activity against a customer record
After a call or email, an agent attaches a note to the relevant Keap contact and records the email that was sent, building a timeline on the customer record. Reading a contact's tags lets the agent decide which follow-up applies. This keeps sales history in one place without a person updating the CRM by hand.
Add a note summarising a call to a given contact and list the tags currently applied to that contact
Create orders for a customer
When a sale closes, an agent creates an order in Keap against the customer's contact, so revenue and fulfilment data live alongside the CRM record. It can also read orders back to check status. This links the customer's profile to what they have bought without switching tools.
Create an order for a given contact and return the order id
Key Endpoints
281 endpoints — the keap api is the rest interface to keap's crm and sales-and-marketing platform for small businesses.
METHOD
PATH
DESCRIPTION
GET
/rest/v2/contacts
List contacts in the account
POST
/rest/v2/contacts
Create a new contact
PATCH
/rest/v2/contacts/{contact_id}
Update fields on a contact
POST
/rest/v2/contacts/{contact_id}/notes
Attach a note to a contact
GET
/rest/v2/contacts/{contact_id}/tags
List the tags applied to a contact
POST
/rest/v2/orders
Create an order for a customer
GET
/rest/v2/contacts
List contacts in the account
POST
/rest/v2/contacts
Create a new contact
PATCH
/rest/v2/contacts/{contact_id}
Update fields on a contact
POST
/rest/v2/contacts/{contact_id}/notes
Attach a note to a contact
GET
/rest/v2/contacts/{contact_id}/tags
List the tags applied to a contact
POST
/rest/v2/orders
Create an order for a customer
Jentic AI Readiness Score
This API is usable in Jentic One now. Its AI-readiness score against Jentic's framework shows where it stands today and where improvements would make it even easier for agents to use.
K
Keap API
- Foundational (C+)59/100
69
Foundational Compliance68
Developer Experience & Jentic Compatibility53
AI-Readiness & Agent Experience43
Agent Usability90
Security67
AI DiscoverabilityPowered by JenticScoring Framework 1.0.0 | Scoring Engine 0.4.2
Show dimension breakdown
69
Foundational Compliance
Base layer of spec validity and structural soundness.
Grade: B+Signals: 4
77%
Lint Results
Aggregated quality score from linter diagnostics, weighted by severity.
100%
Resolution Completeness
Percentage of `$ref` references that resolve successfully.
0%
Specification Validity
Checks whether the API description parses successfully and conforms to its declared specification (e.g., OpenAPI).
100%
Structural Integrity
Structural correctness score based on schema issues using logarithmic dampening.
68
Developer Experience & Jentic Compatibility
Clarity, completeness, and ingestion readiness for developers and tooling.
Grade: B+Signals: 4
17%
Example Density
How richly the API is illustrated with examples.
80%
Example Validity
Percentage of examples that conform to their schemas.
75%
Response Coverage
Percentage of operations with complete response definitions (success, client error, server error).
100%
Tooling Readiness
Health of API ingestion, bundling, and resolution within Jentic pipelines.
53
AI-Readiness & Agent Experience
Semantic breadth, depth, and agent comprehension for AI systems.
Grade: CSignals: 4
52%
Description Coverage
Coverage of descriptions across API elements.
0%
Error Standardization
Coverage of RFC 9457 Problem Details for error responses.
100%
OperationId Quality
Coverage, uniqueness, and casing consistency of operationIds for AI inference.
61%
Summary Coverage
Coverage of summaries across operations/tags/info.
43
Agent Usability
Functional utility, complexity comfort, and AI orchestration readiness.
Grade: D-Signals: 1
43%
Complexity Comfort
Agent comfort level based on API operational and structural complexity.
90
Security
Trust, risk posture, and security compliance.
Grade: A+Signals: 1
90%
Authentication Strength
Average quality of security schemes based on authentication method strength (weakest link for OAuth2).
67
AI Discoverability
Findability, semantic richness, and reasoning readiness.
Grade: BSignals: 1
67%
Descriptive Richness
Clarity and depth of descriptions across API elements.
Score it yourself
Every API in the directory is allowlisted, so you can re-score it with no key required.
npx @jentic/api-scorecard-cli score <openapi-url>Why Jentic?
What agents get from Jentic-routed access to this vendor.
Setup
Wiring the Keap API by hand means completing its OAuth 2.0 authorization-code flow, refreshing access tokens, and formatting the contact, note, tag, and order calls against the infusionsoft.com host yourself. Through Jentic you install once, import the Keap API from the API Directory, authorise once, and your agent calls it.
Permission scoping
The Keap API addresses each contact by an id in the URL path, so you can scope the agent to the records and operations it needs: allow it to read and update contacts and leave contact deletion out of the allowed set unless you add it.
Credential isolation
Your Keap OAuth token is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context.
Intent-based discovery
Agents search Jentic by intent such as 'create a contact' or 'add a note to a contact', and Jentic returns the matching Keap operation with its input schema so the agent calls the right endpoint without reading the reference docs.
Related APIs
Alternatives and complements available in the Jentic catalogue.
FAQs
Specific to using Keap API through Jentic.
What authentication does the Keap API use?
Keap uses OAuth 2.0 with the authorization-code flow (the oauth2 scheme), so requests carry an access token you obtain by authorising your app against a Keap account. Through Jentic the token is stored encrypted by your own Jentic One instance and supplied to requests at execution time, so the agent never sees the raw value.
Can I manage CRM contacts through the Keap API?
Yes. You can create a contact, read it back, update its fields, and delete it, as well as attach notes and read the tags applied to it. An agent connected through Jentic can keep the CRM current as leads and customer details change.
Does the Keap API still use the Infusionsoft host?
Yes. Keap was formerly called Infusionsoft, and the API base URL still uses the infusionsoft.com host. The endpoints are the current v2 REST operations for contacts, notes, tags, emails, and orders, so the host name is historical rather than a separate product.
What are the rate limits for the Keap API?
The OpenAPI spec does not declare rate limits for the Keap API. Apply conservative client-side throttling, back off on HTTP 429 responses, and check the Keap developer documentation for the current published limits.
Can I limit what my agent is allowed to do with the Keap API?
Yes. You choose which operations the agent may call, so it can be allowed to read and update contacts while contact deletion stays out of the allowed set unless you add it. Because the API addresses each contact by an id in the URL path, you can keep the agent to the records and operations it needs, and every call it makes is logged.
Is there a Keap API MCP server?
You don't need an MCP server to give your agent Keap. Jentic connects it directly from the API Directory: import it, complete the OAuth authorisation once, and your agent calls the contact, note, and order operations on demand without a separate server to run.
How do I manage Keap contacts through Jentic?
Search Jentic for an intent like 'create a contact' or 'add a note to a contact', which returns the matching Keap operation with its input schema so the agent supplies the contact details and reads the response. To run it on your own infrastructure, install Jentic One from its GitHub repo.
GET STARTED