How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Infusionsoft (Keap) Users API

Users-Endpoint

Infusionsoft (Keap) Users API is one of 59 APIs that Infusionsoft (Keap) publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include User. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, an API reference, and authentication docs.

This API exposes 16 operations across 12 paths, and defines 29 schemas. It is described by OpenAPI 3.2.0, at version 1.0.

Requests are made against 3 base URLs: https://api.keap.com/crm, https://api.infusionsoft.com/crm/rest, https://api.infusionsoft.com/crm.

16 operations 12 paths 29 schemas 12 GET2 PATCH2 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
1.0
Base URL
https://api.infusionsoft.com/crm/rest/v2
Authentication
OAuth 2.0
License
Resource Areas
1

Authentication & Security 1

Infusionsoft (Keap) Users API declares 1 security scheme for authenticating requests. It supports OAuth 2.0 (oauth2) using the authorizationCode flow.

Paths & Operations 16

Across 12 paths, the API surfaces 16 operations — 12 GET, 2 PATCH, 2 POST. Each is listed below with its method, path, parameters, and response codes.

Users 16
GET
/rest/v2/users/{user_id}
Get User
getUserById 1 param → 200400401403404405409500
PATCH
/rest/v2/users/{user_id}
Update User
updateUser 2 params body → 200400401403404405409500
GET
/rest/v2/users
List Users
listPaginatedUsers 4 params → 200400401403404405409500
GET
/rest/v2/users/{user_id}/signature
Get User email signature
getUserSignature 1 param → 200400401403404405409500
GET
/rest/v2/oauth/connect/userinfo
Retrieve User Info
getUserInfo → 200400401403404405409500
GET
/v1/users
List Users
listUsersUsingGET 4 params → 200401403404500
POST
/v1/users
Create a User
createUserUsingPOST body → 201401403500
GET
/v1/users/{userId}/signature
Get User email signature
getUserSignatureUsingGET 1 param → 200401403404500
GET
/rest/v1/users
List Users
listUsers 1 param → 400401500403409404501405
POST
/rest/v1/users
Create a User
createUser body → 400401500403409404501405
GET
/rest/v1/users/{userId}/signature
Get User email signature
getUserSignature 1 param → 400401500403409404501405
GET
/v2/oauth/connect/userinfo
Retrieve User Info
getUserInfoUsingGET_1 → 200401403404500
GET
/v2/users
List Users
listPaginatedUsersUsingGET 4 params → 200401403404500
GET
/v2/users/{user_id}
Get User
getUserByIdUsingGET 1 param → 200401403404500
PATCH
/v2/users/{user_id}
Update User
updateUserUsingPATCH 2 params body → 200401403404500
GET
/v2/users/{user_id}/signature
Get User email signature
getUserSignatureUsingGET_1 1 param → 200401403404500

Schemas 29

The contract defines 29 schemas that model the data the API accepts and returns. The most detailed are User (24 properties), RestUser (21 properties), RestUser_2 (21 properties), Address (11 properties). Each schema is shown below with its type and property counts.

User
object
A user in the system
24 properties
Address
object
11 properties
EmailAddressRequest
object
3 properties
Error
object
4 properties
ErrorDetails
object
2 properties
GetUserInfoResponse
object
User information response
10 properties
SocialAccount
object
2 properties 1 required
ListUsersPaginatedResponse
object
Paginated response containing a list of users
2 properties
EmailAddress
object
5 properties
PhoneNumber
object
5 properties
UpdateUserRequest
object
user
10 properties
FaxNumber
object
3 properties
Throwable
object
5 properties
Address_2
object
7 properties
CreateUser
object
user
4 properties 2 required
Users
object
4 properties
DefaultHttpStatusCode
ModelAndView
object
7 properties
HttpStatusCode
object
6 properties
HttpStatus
RestUser
object
21 properties 1 required
PhoneNumber_2
object
5 properties 1 required
View
object
1 property
FaxNumber_2
object
3 properties 1 required
RestUserQueryCommand
object
6 properties
Address_3
object
7 properties
RestUser_2
object
21 properties 1 required
PhoneNumber_3
object
5 properties 1 required
FaxNumber_3
object
3 properties 1 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

infusionsoft-users-api-openapi.yml Raw ↑

Other APIs Infusionsoft (Keap) publishes across the network.

Infusionsoft XML-RPC API
Infusionsoft (Keap) Account Info API
Infusionsoft (Keap) Affiliate API
Infusionsoft (Keap) Appointment API
Infusionsoft (Keap) Automation API
Infusionsoft (Keap) Automation Category API
Infusionsoft (Keap) Business Profile API
Infusionsoft (Keap) Campaign API
Infusionsoft (Keap) Category Discounts API
Infusionsoft (Keap) Company API
Infusionsoft (Keap) Contact API
Infusionsoft (Keap) Custom Fields API
Where this information came from

This is an independent, third-party profile of Infusionsoft (Keap) Users API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.