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) Lead Source Recurring Expenses API

The Lead Source Recurring Expenses API from Infusionsoft (Keap) — 3 operation(s) for lead source recurring expenses.

Infusionsoft (Keap) Lead Source Recurring Expenses 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 Lead Source Recurring Expenses. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, an API reference, and authentication docs.

This API exposes 12 operations across 6 paths, and defines 10 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.

12 operations 6 paths 10 schemas 2 DELETE6 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) Lead Source Recurring Expenses API declares 1 security scheme for authenticating requests. It supports OAuth 2.0 (oauth2) using the authorizationCode flow.

Paths & Operations 12

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

Lead Source Recurring Expenses 12
GET
/rest/v2/leadSources/{lead_source_id}/recurringExpenses
Retrieves a list of lead source recurring expenses
listLeadSourceRecurringExpenses 5 params → 200400401403404405409500
POST
/rest/v2/leadSources/{lead_source_id}/recurringExpenses
Create a Lead Source Recurring Expense
createLeadSourceRecurringExpense 1 param body → 201400401403404405409500
GET
/rest/v2/leadSources/{lead_source_id}/recurringExpenses/{lead_source_recurring_expense_id}
Retrieve a Lead Source Recurring Expense
getLeadSourceRecurringExpense 2 params → 200400401403404405409500
DELETE
/rest/v2/leadSources/{lead_source_id}/recurringExpenses/{lead_source_recurring_expense_id}
Delete a Lead Source Recurring Expense
deleteLeadSourceRecurringExpense 2 params → 204400401403404405409500
PATCH
/rest/v2/leadSources/{lead_source_id}/recurringExpenses/{lead_source_recurring_expense_id}
Update a Lead Source Recurring Expense
updateLeadSourceRecurringExpense 3 params body → 200400401403404405409500
GET
/rest/v2/leadSources/{lead_source_id}/recurringExpenses/{lead_source_recurring_expense_id}/expenses
Retrieves a list of expenses incurred from a recurring expense
listExpensesIncurredFromLeadSourceRecurringExpense 6 params → 200400401403404405409500
GET
/v2/leadSources/{lead_source_id}/recurringExpenses
Retrieves a list of lead source recurring expenses
listLeadSourceRecurringExpensesUsingGET 5 params → 200400401403404500
POST
/v2/leadSources/{lead_source_id}/recurringExpenses
Create a Lead Source Recurring Expense
createLeadSourceRecurringExpenseUsingPOST 1 param body → 201400401403500
GET
/v2/leadSources/{lead_source_id}/recurringExpenses/{lead_source_recurring_expense_id}
Retrieve a Lead Source Recurring Expense
getLeadSourceRecurringExpenseUsingGET 2 params → 200401403404500
DELETE
/v2/leadSources/{lead_source_id}/recurringExpenses/{lead_source_recurring_expense_id}
Delete a Lead Source Recurring Expense
deleteLeadSourceRecurringExpenseUsingDELETE 2 params → 204401403404500
PATCH
/v2/leadSources/{lead_source_id}/recurringExpenses/{lead_source_recurring_expense_id}
Update a Lead Source Recurring Expense
updateLeadSourceRecurringExpenseUsingPATCH 3 params body → 200400401403404500
GET
/v2/leadSources/{lead_source_id}/recurringExpenses/{lead_source_recurring_expense_id}/expenses
Retrieves a list of expenses incurred from a recurring expense
listExpensesIncurredFromLeadSourceRecurringExpenseUsingGET 6 params → 200400401403404500

Schemas 10

The contract defines 10 schemas that model the data the API accepts and returns. The most detailed are LeadSourceRecurringExpense (10 properties), LeadSourceExpense (9 properties), Throwable (5 properties), LeadSourceRecurringExpenseUpdateRequest (5 properties). Each schema is shown below with its type and property counts.

Error
object
4 properties
LeadSourceExpense
object
9 properties
ErrorDetails
object
2 properties
CurrencyValue
object
3 properties
CreateLeadSourceRecurringExpenseRequest
object
5 properties 1 required
ListLeadSourceRecurringExpensesResponse
object
2 properties
LeadSourceRecurringExpense
object
10 properties
LeadSourceRecurringExpenseUpdateRequest
object
5 properties
ListLeadSourceExpensesResponse
object
2 properties
Throwable
object
5 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

infusionsoft-lead-source-recurring-expenses-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) Lead Source Recurring Expenses 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.