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

Increase Lockbox Recipients API

Lockbox Recipients represent an inbox at a Lockbox Address. Checks received for a Lockbox Recipient are deposited into its associated Account.

Increase Lockbox Recipients API is one of 57 APIs that Increase publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Lockbox Recipients. The published artifact set on APIs.io includes an OpenAPI specification and API documentation.

This API exposes 4 operations across 2 paths, and defines 5 schemas. It is described by OpenAPI 3.2.0, at version 0.0.1.

Requests are made against 2 base URLs: https://api.increase.com, https://sandbox.increase.com.

4 operations 2 paths 5 schemas 2 GET1 PATCH1 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
0.0.1
Base URL
https://api.increase.com
Authentication
HTTP Bearer
Resource Areas
1

Authentication & Security 1

Increase Lockbox Recipients API declares 1 security scheme for authenticating requests. It accepts HTTP bearer tokens (bearerAuth). By default, every request must be authenticated.

Paths & Operations 4

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

Lockbox Recipients 4

Lockbox Recipients represent an inbox at a Lockbox Address. Checks received for a Lockbox Recipient are deposited into its associated Account.

GET
/lockbox_recipients
List Lockbox Recipients
list_lockbox_recipients 9 params → 2004XX5XX
POST
/lockbox_recipients
Create a Lockbox Recipient
create_a_lockbox_recipient body → 2004XX5XX
GET
/lockbox_recipients/{lockbox_recipient_id}
Retrieve a Lockbox Recipient
retrieve_a_lockbox_recipient 1 param → 2004XX5XX
PATCH
/lockbox_recipients/{lockbox_recipient_id}
Update a Lockbox Recipient
update_a_lockbox_recipient 1 param body → 2004XX5XX

Schemas 5

The contract defines 5 schemas that model the data the API accepts and returns. The most detailed are lockbox_recipient (10 properties), create_a_lockbox_recipient_parameters (4 properties), update_a_lockbox_recipient_parameters (3 properties), lockbox_recipient_list (2 properties). Each schema is shown below with its type and property counts.

create_a_lockbox_recipient_parameters
object
4 properties 2 required
lockbox_recipient_list
object
A list of Lockbox Recipient objects.
2 properties 2 required
update_a_lockbox_recipient_parameters
object
3 properties
error
lockbox_recipient
object
Lockbox Recipients represent an inbox at a Lockbox Address. Checks received for a Lockbox Recipient are deposited into its associated Account.
10 properties 10 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

increase-lockbox-recipients-api-openapi.yml Raw ↑

Other APIs Increase publishes across the network.

Increase Account Numbers API
Increase Account Statements API
Increase Account Transfers API
Increase Accounts API
Increase Ach Prenotifications API
Increase Ach Transfers API
Increase Card Disputes API
Increase Card Payments API
Increase Card Purchase Supplements API
Increase Card Push Transfers API
Increase Card Tokens API
Increase Card Validations API
Where this information came from

This is an independent, third-party profile of Increase Lockbox Recipients 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.