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) Tags API

Tag-Company-Endpoint

This API exposes 46 operations across 28 paths, and defines 45 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.

46 operations 28 paths 45 schemas 8 DELETE20 GET4 PATCH14 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) Tags API declares 1 security scheme for authenticating requests. It supports OAuth 2.0 (oauth2) using the authorizationCode flow.

Paths & Operations 46

Across 28 paths, the API surfaces 46 operations — 8 DELETE, 20 GET, 4 PATCH, 14 POST. Each is listed below with its method, path, parameters, and response codes.

Tags 46
GET
/rest/v2/tags
List Tags
listTags 4 params → 200400401403404405409500
POST
/rest/v2/tags
Create Tag
createTag body → 201400401403404405409500
POST
/rest/v2/tags/{tag_id}/contacts:removeTags
Remove Tags
removeTags 1 param body → 204400401403404405409500
POST
/rest/v2/tags/{tag_id}/contacts:applyTags
Apply Tag
applyTags 1 param body → 200400401403404405409500
GET
/rest/v2/tags/categories
List Tag Categories
listTagCategories 4 params → 200400401403404405409500
POST
/rest/v2/tags/categories
Create Tag Category
createTagCategory body → 201400401403404405409500
GET
/rest/v2/tags/{tag_id}
Retrieve a Tag
getTag 1 param → 200400401403404405409500
DELETE
/rest/v2/tags/{tag_id}
Delete Tag
deleteTag 1 param → 204400401403404405409500
PATCH
/rest/v2/tags/{tag_id}
Update a Tag
updateTag 2 params body → 200400401403404405409500
GET
/rest/v2/tags/categories/{tag_category_id}
Retrieve a Tag Category
getCategory 1 param → 200400401403404405409500
DELETE
/rest/v2/tags/categories/{tag_category_id}
Delete Tag Category
deleteTagCategory 1 param → 204400401403404405409500
PATCH
/rest/v2/tags/categories/{tag_category_id}
Update a Tag Category
updateTagCategory 2 params body → 200400401403404405409500
GET
/rest/v2/tags/{tag_id}/contacts
List Tagged Contacts
listContactsWithTagId 5 params → 200400401403404405409500
GET
/rest/v2/tags/{tag_id}/companies
List Tagged Companies
listCompaniesForTagId 5 params → 200400401403404405409500
GET
/v1/tags
List Tags
listTagsUsingGET 4 params → 200401403404500
POST
/v1/tags
Create Tag
createTagUsingPOST body → 200401403500
POST
/v1/tags/categories
Create Tag Category
createTagCategoryUsingPOST body → 200401403500
GET
/v1/tags/{id}
Retrieve a Tag
getTagUsingGET 1 param → 200401403404500
GET
/v1/tags/{tagId}/companies
List Tagged Companies
listCompaniesForTagIdUsingGET 3 params → 200401403404500
GET
/v1/tags/{tagId}/contacts
List Tagged Contacts
listContactsForTagIdUsingGET 3 params → 200401403404500
POST
/v1/tags/{tagId}/contacts
Apply Tag to Contacts
applyTagToContactIdsUsingPOST 1 param body → 200401403500
DELETE
/v1/tags/{tagId}/contacts
Remove Tag from Contacts
removeTagFromContactIdsUsingDELETE 2 params → 204401403404500
DELETE
/v1/tags/{tagId}/contacts/{contactId}
Remove Tag from Contact
removeTagFromContactIdUsingDELETE 2 params → 204401403404500
GET
/rest/v1/tags/{tagId}/contacts
List Tagged Contacts
listContactsForTagId 2 params → 400401500403409404501405
POST
/rest/v1/tags/{tagId}/contacts
Apply Tag to Contacts
applyTagToContactIds 1 param body → 400401500403409404501405
DELETE
/rest/v1/tags/{tagId}/contacts
Remove Tag from Contacts
removeTagFromContactIds 2 params → 400401500403409404501405
POST
/rest/v1/tags/categories
Create Tag Category
postRestV1TagsCategories body → 400401500403409404501405
GET
/rest/v1/tags
List Tags
getRestV1Tags 1 param → 400401500403409404501405
POST
/rest/v1/tags
Create Tag
postRestV1Tags body → 400401500403409404501405
GET
/rest/v1/tags/{tagId}/companies
List Tagged Companies
getRestV1TagsByTagIdCompanies 2 params → 400401500403409404501405
GET
/rest/v1/tags/{id}
Retrieve a Tag
getRestV1TagsById 1 param → 400401500403409404501405
DELETE
/rest/v1/tags/{tagId}/contacts/{contactId}
Remove Tag from Contact
removeTagFromContactId 2 params → 400401500403409404501405
GET
/v2/tags
List Tags
listTagsUsingGET_1 4 params → 200401403404500
POST
/v2/tags
Create Tag
createTagUsingPOST_1 body → 201401403500
GET
/v2/tags/categories
List Tag Categories
listTagCategoriesUsingGET 4 params → 200401403404500
POST
/v2/tags/categories
Create Tag Category
createTagCategoryUsingPOST_1 body → 201401403500
GET
/v2/tags/categories/{tag_category_id}
Retrieve a Tag Category
getCategoryUsingGET 1 param → 200401403404500
DELETE
/v2/tags/categories/{tag_category_id}
Delete Tag Category
deleteTagCategoryUsingDELETE 1 param → 204401403404500
PATCH
/v2/tags/categories/{tag_category_id}
Update a Tag Category
updateTagCategoryUsingPATCH 2 params body → 200401403404500
GET
/v2/tags/{tag_id}
Retrieve a Tag
getTagUsingGET_1 1 param → 200401403404500
DELETE
/v2/tags/{tag_id}
Delete Tag
deleteTagUsingDELETE 1 param → 204401403404500
PATCH
/v2/tags/{tag_id}
Update a Tag
updateTagUsingPATCH 2 params body → 200401403404500
GET
/v2/tags/{tag_id}/companies
List Tagged Companies
listCompaniesForTagIdUsingGET_1 5 params → 200401403404500
GET
/v2/tags/{tag_id}/contacts
List Tagged Contacts
listContactsWithTagIdUsingGET 5 params → 200401403404500
POST
/v2/tags/{tag_id}/contacts:applyTags
Apply Tag
applyTagsUsingPOST 1 param body → 200401403500
POST
/v2/tags/{tag_id}/contacts:removeTags
Remove Tags
removeTagsUsingPOST 1 param body → 204401403500

Schemas 45

The contract defines 45 schemas that model the data the API accepts and returns. The most detailed are Company (31 properties), Address (11 properties), ModelAndView (7 properties), Tag (6 properties). Each schema is shown below with its type and property counts.

TagCategory
object
5 properties
PhoneNumber
object
5 properties
CustomFieldValue
object
2 properties
EmailAddress
object
5 properties
Error
object
4 properties
TaggedCompany
object
2 properties
TaggedContact
object
5 properties
ApplyRemoveTagRequest
object
1 property 1 required
FaxNumber
object
3 properties
UpdateTagResponse
object
6 properties
GetTagCategoryResponse
object
5 properties
CreateUpdateTagRequest
object
tag
3 properties
CategoryReference
object
1 property 1 required
Tag
object
6 properties
ListTagCategoriesResponse
object
2 properties
ErrorDetails
object
2 properties
ListTaggedCompaniesResponse
object
2 properties
ListTaggedContactsResponse
object
2 properties
UpdateTagCategoryResponse
object
5 properties
Company
object
31 properties
Address
object
11 properties
ApplyTagsResponse
object
1 property
ListTagsResponse
object
2 properties
CreateUpdateTagCategoryRequest
object
tagCategory
2 properties
Throwable
object
5 properties
TagCategory_2
object
3 properties 2 required
View
object
1 property
CreateTag
object
3 properties 1 required
TaggedCompany_2
object
2 properties
TaggedContact_2
object
2 properties
ModelAndView
object
7 properties
BasicCompany
object
3 properties
CreateTagCategory
object
2 properties 1 required
TaggedCompanyList
object
4 properties
Tags
object
4 properties
DefaultHttpStatusCode
CategoryReference_2
object
1 property 1 required
Tag_2
object
4 properties 2 required
HttpStatusCode
object
6 properties
RestQueryCommand
object
2 properties
BasicContact
object
4 properties
HttpStatus
RestTagQueryCommand
object
4 properties
TaggedContactList
object
4 properties
SetOfIds
object
1 property 1 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

infusionsoft-tags-api-openapi.yml Raw ↑
Where this information came from

This is an independent, third-party profile of Infusionsoft (Keap) Tags 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.