Increase is a banking and payments API providing direct ACH, wire, RTP, FedNow, check, and card programs. Bank-direct connectivity (no aggregator middle layer).
Increase publishes 57 API contracts indexed on the APIs.io network, including Account Numbers API, Account Statements API, Account Transfers API, and 54 more. Tagged areas include Fintech, Banking, Payments, ACH, and Wires.
The Increase catalog on APIs.io includes 1 Spectral governance ruleset.
Increase’s developer surface includes pricing, sandbox, API reference, authentication, engineering blog, and 17 more developer resources.
Regulatory Posture applies to this provider. Its tags matched the
Banking & Open Finance regime, so
Regulatory Posture carries 15 points of the composite.
If this regime is wrong for your business, say so on your
provider repo — the
applicability map is public and we will correct it.
Create-or-Update Ergonomics applies to this provider. This API accepts writes, so it
carries 10 points of the composite. It is scored from the published contracts
themselves: whether a caller can create-or-update in one call, whether the write accepts a key the caller already
holds, and whether the response says which branch ran. Without that, every write needs a search-and-branch in
front of it, and the first time that check is skipped a duplicate record is created.
Scored against the observed mean rather than raw — a provider at the catalog average is unchanged by this facet,
not penalised by it.
The six quality facets above are damped to 75 points between them,
because the conditional facet above carries the other
25. That is why each facet's contribution is shown against a damped
maximum: raising a quality facet moves the composite by 75% of its nominal
weight, not 100%. The full arithmetic is at apis.io/rating/.
Show this score on your site.
It updates itself when the score changes. Paste this where you link to your API docs:
<a href="https://apis.io/providers/increase/"><img src="https://apis.io/badge/increase/card.svg" alt="Increase on APIs.io — Kin Score by API Evangelist"></a>
Other styles, a README pill and a shields.io endpoint are on the badge page.
Raise your score.
Agent readiness — checks not met, largest first (exact, from this profile):
MCP Server+12 pts — deployment.mode + probe verdict on the mcp/ manifest, not the pointer; an unprobed slug falls back to authorship Ask about this →
Idempotency+9 pts — OpenAPI mutating operations declare an idempotency key — a header, a request-body property, or a named de-duplication token whose own description says so (verified); else common[].type matches /idempoten/i (documented) Ask about this →
Stable Error Semantics+8 pts — OpenAPI $refs a shared error schema across 4xx/5xx responses (verified), else common[].type includes ErrorCatalog / ErrorCodes / DeclineCodes Ask about this →
Delegated User Identity+6 pts — a served discovery document listing authorization_code in grant_types_supported (served), else an oauth2 authorizationCode flow or openIdConnect declared in an OpenAPI (documented) Ask about this →
6 more unmet checks in the Agent Readiness table above.
Kin Score — facets with the most composite points still available (weight × headroom):
Each check links to what satisfies it. Publish the artifact, or tell us where it already lives, and the score moves on the next scoring run.
Not sure how this applies to your stack? Ask about any one item. Kin Lane reads every question, looks at your profile and your situation, and replies with what a fix would take — scoped to that one area, priced up front, yours whether you ship it or not. Ask a question →
The Kin Score Market layer reads a provider inside its market:
its position, and how deep its integrations go. Depth is only comparable within a position. Provisional and unweighted:
not part of the Kin Score or agent readiness.
Registered MCP server and declares compatibility are report only — not weighted.
Undeclared means we found nothing we can read, so there is no number: we never infer integrations.
Standards this provider implements or carries. De facto ones are profiled and measured by the API Commons; formal ones come from the standards directory and are linked by the provider's own tags. The evidence column says how each claim was established — not that it was made.
Each account can have multiple account and routing numbers. We recommend that you use a set per vendor. This is similar to how you use different passwords for different websites...
Account Statements are generated monthly for every active Account. You can access the statement's data via the API or retrieve a PDF with its details via its associated File.
Account transfers move funds between your own accounts at Increase (accounting systems often refer to these as Book Transfers). Account Transfers are free and synchronous. Upon ...
Accounts are your bank accounts with Increase. They store money, receive transfers, and send payments. They earn interest and have depository insurance.
Cards may operate on credit, debit, or prepaid BINs. They’ll immediately work for online purchases after you create them. All cards work on a good funds model, and maintain a ma...
Declined Transactions are refused additions and removals of money from your bank account. For example, Declined Transactions are caused when your Account has an insufficient bal...
This contains artwork and metadata relating to a Card's appearance in digital wallet apps like Apple Pay and Google Pay. For more information, see our guide on [digital card art...
A Digital Wallet Token is created when a user adds a Card to their Apple Pay or Google Pay app. The Digital Wallet Token can be used for purchases just like a Card.
Entities are the legal entities that own accounts. They can be people, corporations, partnerships, government authorities, or trusts. To learn more, see [Entities](/documentatio...
Entity Onboarding Sessions let your customers onboard themselves by completing Increase-hosted forms. Create a session and redirect your customer to the returned URL. When they'...
Webhooks are event notifications we send to you by HTTPS POST requests. Event Subscriptions are how you configure your application to listen for them. You can create an Event Su...
Events are records of things that happened to objects at Increase. Events are accessible via the List Events endpoint and can be delivered to your application via webhooks. For ...
Exports are generated files. Some exports can contain a lot of data, like a CSV of your transactions. Others can be a single document, like a tax form. Since they can take a whi...
Files are objects that represent a file hosted on Increase's servers. The file may have been uploaded by you (for example, when uploading a check image) or it may have been crea...
Groups represent organizations using Increase. You can retrieve information about your own organization via the API. More commonly, OAuth platforms can retrieve information abou...
Inbound wire drawdown requests are requests from someone else to send them a wire. For more information, see our [Wire Drawdown Requests documentation](/documentation/wire-drawd...
Pending Transactions are potential future additions and removals of money from your bank account. They impact your available balance, but not your current balance. To learn more...
This contains artwork and metadata relating to a Physical Card's appearance. For more information, see our guide on [physical card artwork](https://increase.com/documentation/ca...
Custom physical Visa cards that are shipped to your customers. The artwork is configurable by a connected [Card Profile](/documentation/api#card-profiles). The same Card can be ...
Programs determine the compliance and commercial terms of Accounts. By default, you have a Commercial Banking program for managing your own funds. If you are lending or managing...
Transactions are the immutable additions and removals of money from your bank account. They're the equivalent of line items on your bank statement. To learn more, see [Transacti...
Wire drawdown requests enable you to request that someone else send you a wire. Because there is nuance to making sure your counterparty's bank processes these correctly, we ask...
aid: increase
url: https://raw.githubusercontent.com/api-evangelist/increase/refs/heads/main/apis.yml
name: Increase
kind: company
description: Increase is a banking and payments API providing direct ACH, wire, RTP, FedNow, check, and card programs. Bank-direct
connectivity (no aggregator middle layer).
deliveryModel:
model: saas
open_source: false
commercial: true
callable_host: true
label: Hosted service · you call their endpoint
confidence: high
source:
- openapi
- pricing
generated: '2026-08-28'
method: derived
accessModel:
pricing: paid
onboarding: unknown
trial: false
try_now: false
public: false
label: Paid
confidence: high
source:
- plans
- authentication
- rate-limits
- security
generated: '2026-11-13'
method: derived
image: https://kinlane-images.s3.amazonaws.com/shared/apis-json/icons/increase.png
tags:
- Fintech
- Banking
- Payments
- ACH
- Wires
- Embedded Finance
created: '2026-05-08'
modified: '2026-09-16'
specificationVersion: '0.23'
apis:
- aid: increase:increase-account-numbers-api
name: Increase Account Numbers API
description: Each account can have multiple account and routing numbers. We recommend that you use a set per vendor. This
is similar to how you use different passwords for different websites. Account numbers can also be used to seamlessly reconcile
inbound payments. Generating a unique account number per vendor ensures you always know the originator of an incoming
payment.
humanURL: https://increase.com/documentation/api
baseURL: https://api.increase.com
tags:
- Account Numbers
properties:
- type: OpenAPI
url: openapi/increase-account-numbers-api-openapi.yml
- type: Documentation
url: https://increase.com/documentation/api
- aid: increase:increase-account-statements-api
name: Increase Account Statements API
description: Account Statements are generated monthly for every active Account. You can access the statement's data via
the API or retrieve a PDF with its details via its associated File.
humanURL: https://increase.com/documentation/api
baseURL: https://api.increase.com
tags:
- Account Statements
properties:
- type: OpenAPI
url: openapi/increase-account-statements-api-openapi.yml
- type: Documentation
url: https://increase.com/documentation/api
- aid: increase:increase-account-transfers-api
name: Increase Account Transfers API
description: Account transfers move funds between your own accounts at Increase (accounting systems often refer to these
as Book Transfers). Account Transfers are free and synchronous. Upon creation they create two Transactions, one negative
on the originating account and one positive on the destination account (unless the transfer requires approval, in which
case the Transactions will be created when the transfer is approved).
humanURL: https://increase.com/documentation/api
baseURL: https://api.increase.com
tags:
- Account Transfers
properties:
- type: OpenAPI
url: openapi/increase-account-transfers-api-openapi.yml
- type: Documentation
url: https://increase.com/documentation/api
- aid: increase:increase-accounts-api
name: Increase Accounts API
description: Accounts are your bank accounts with Increase. They store money, receive transfers, and send payments. They
earn interest and have depository insurance.
humanURL: https://increase.com/documentation/api
baseURL: https://api.increase.com
tags:
- Account
tags_raw:
- Accounts
properties:
- type: OpenAPI
url: openapi/increase-accounts-api-openapi.yml
- type: Documentation
url: https://increase.com/documentation/api
- aid: increase:increase-ach-prenotifications-api
name: Increase Ach Prenotifications API
description: The Ach Prenotifications API from Increase — 2 operation(s) for ach prenotifications.
humanURL: https://increase.com/documentation/api
baseURL: https://api.increase.com
tags:
- Ach Prenotifications
properties:
- type: OpenAPI
url: openapi/increase-ach-prenotifications-api-openapi.yml
- type: Documentation
url: https://increase.com/documentation/api
- aid: increase:increase-ach-transfers-api
name: Increase Ach Transfers API
description: The Ach Transfers API from Increase — 4 operation(s) for ach transfers.
humanURL: https://increase.com/documentation/api
baseURL: https://api.increase.com
tags:
- ACH Transfers
tags_raw:
- Ach Transfers
properties:
- type: OpenAPI
url: openapi/increase-ach-transfers-api-openapi.yml
- type: Documentation
url: https://increase.com/documentation/api
- aid: increase:increase-card-disputes-api
name: Increase Card Disputes API
description: If unauthorized activity occurs on a card, you can create a Card Dispute and we'll work with the card networks
to return the funds if appropriate.
humanURL: https://increase.com/documentation/api
baseURL: https://api.increase.com
tags:
- Card Disputes
properties:
- type: OpenAPI
url: openapi/increase-card-disputes-api-openapi.yml
- type: Documentation
url: https://increase.com/documentation/api
- aid: increase:increase-card-payments-api
name: Increase Card Payments API
description: Card Payments group together interactions related to a single card payment, such as an authorization and its
corresponding settlement.
humanURL: https://increase.com/documentation/api
baseURL: https://api.increase.com
tags:
- Card Payments
properties:
- type: OpenAPI
url: openapi/increase-card-payments-api-openapi.yml
- type: Documentation
url: https://increase.com/documentation/api
- aid: increase:increase-card-purchase-supplements-api
name: Increase Card Purchase Supplements API
description: Additional information about a card purchase (e.g., settlement or refund), such as level 3 line item data.
humanURL: https://increase.com/documentation/api
baseURL: https://api.increase.com
tags:
- Card Purchase Supplements
properties:
- type: OpenAPI
url: openapi/increase-card-purchase-supplements-api-openapi.yml
- type: Documentation
url: https://increase.com/documentation/api
- aid: increase:increase-card-push-transfers-api
name: Increase Card Push Transfers API
description: Card Push Transfers send funds to a recipient's payment card in real-time.
humanURL: https://increase.com/documentation/api
baseURL: https://api.increase.com
tags:
- Card Push Transfers
properties:
- type: OpenAPI
url: openapi/increase-card-push-transfers-api-openapi.yml
- type: Documentation
url: https://increase.com/documentation/api
- aid: increase:increase-card-tokens-api
name: Increase Card Tokens API
description: Card Tokens represent a tokenized card number that can be used for Card Push Transfers and Card Validations.
humanURL: https://increase.com/documentation/api
baseURL: https://api.increase.com
tags:
- Card Tokens
properties:
- type: OpenAPI
url: openapi/increase-card-tokens-api-openapi.yml
- type: Documentation
url: https://increase.com/documentation/api
- aid: increase:increase-card-validations-api
name: Increase Card Validations API
description: Card Validations are used to validate a card and its cardholder before sending funds to or pulling funds from
a card.
humanURL: https://increase.com/documentation/api
baseURL: https://api.increase.com
tags:
- Card Validations
properties:
- type: OpenAPI
url: openapi/increase-card-validations-api-openapi.yml
- type: Documentation
url: https://increase.com/documentation/api
- aid: increase:increase-cards-api
name: Increase Cards API
description: Cards may operate on credit, debit, or prepaid BINs. They’ll immediately work for online purchases after you
create them. All cards work on a good funds model, and maintain a maximum limit of 100% of the Account’s available balance
at the time of transaction. Funds are deducted from the Account upon transaction settlement.
humanURL: https://increase.com/documentation/api
baseURL: https://api.increase.com
tags:
- Cards
properties:
- type: OpenAPI
url: openapi/increase-cards-api-openapi.yml
- type: Documentation
url: https://increase.com/documentation/api
- aid: increase:increase-check-deposits-api
name: Increase Check Deposits API
description: Check Deposits allow you to deposit images of paper checks into your account.
humanURL: https://increase.com/documentation/api
baseURL: https://api.increase.com
tags:
- Check Deposits
properties:
- type: OpenAPI
url: openapi/increase-check-deposits-api-openapi.yml
- type: Documentation
url: https://increase.com/documentation/api
- aid: increase:increase-check-transfers-api
name: Increase Check Transfers API
description: Check Transfers move funds from your Increase account by mailing a physical check.
humanURL: https://increase.com/documentation/api
baseURL: https://api.increase.com
tags:
- Check Transfers
properties:
- type: OpenAPI
url: openapi/increase-check-transfers-api-openapi.yml
- type: Documentation
url: https://increase.com/documentation/api
- aid: increase:increase-declined-transactions-api
name: Increase Declined Transactions API
description: Declined Transactions are refused additions and removals of money from your bank account. For example, Declined
Transactions are caused when your Account has an insufficient balance or your Limits are triggered.
humanURL: https://increase.com/documentation/api
baseURL: https://api.increase.com
tags:
- Declined Transactions
properties:
- type: OpenAPI
url: openapi/increase-declined-transactions-api-openapi.yml
- type: Documentation
url: https://increase.com/documentation/api
- aid: increase:increase-digital-card-profiles-api
name: Increase Digital Card Profiles API
description: This contains artwork and metadata relating to a Card's appearance in digital wallet apps like Apple Pay and
Google Pay. For more information, see our guide on [digital card artwork](https://increase.com/documentation/card-art).
humanURL: https://increase.com/documentation/api
baseURL: https://api.increase.com
tags:
- Digital Card Profiles
properties:
- type: OpenAPI
url: openapi/increase-digital-card-profiles-api-openapi.yml
- type: Documentation
url: https://increase.com/documentation/api
- aid: increase:increase-digital-wallet-tokens-api
name: Increase Digital Wallet Tokens API
description: A Digital Wallet Token is created when a user adds a Card to their Apple Pay or Google Pay app. The Digital
Wallet Token can be used for purchases just like a Card.
humanURL: https://increase.com/documentation/api
baseURL: https://api.increase.com
tags:
- Digital Wallet Tokens
properties:
- type: OpenAPI
url: openapi/increase-digital-wallet-tokens-api-openapi.yml
- type: Documentation
url: https://increase.com/documentation/api
- aid: increase:increase-entities-api
name: Increase Entities API
description: Entities are the legal entities that own accounts. They can be people, corporations, partnerships, government
authorities, or trusts. To learn more, see [Entities](/documentation/entities).
humanURL: https://increase.com/documentation/api
baseURL: https://api.increase.com
tags:
- Entities
properties:
- type: OpenAPI
url: openapi/increase-entities-api-openapi.yml
- type: Documentation
url: https://increase.com/documentation/api
- aid: increase:increase-entity-beneficial-owners-api
name: Increase Entity Beneficial Owners API
description: The Entity Beneficial Owners API from Increase — 3 operation(s) for entity beneficial owners.
humanURL: https://increase.com/documentation/api
baseURL: https://api.increase.com
tags:
- Entity Beneficial Owners
properties:
- type: OpenAPI
url: openapi/increase-entity-beneficial-owners-api-openapi.yml
- type: Documentation
url: https://increase.com/documentation/api
- aid: increase:increase-entity-onboarding-sessions-api
name: Increase Entity Onboarding Sessions API
description: Entity Onboarding Sessions let your customers onboard themselves by completing Increase-hosted forms. Create
a session and redirect your customer to the returned URL. When they're done, they'll be redirected back to your site.
This API is used for [hosted onboarding](/documentation/hosted-onboarding).
humanURL: https://increase.com/documentation/api
baseURL: https://api.increase.com
tags:
- Entity Onboarding Sessions
properties:
- type: OpenAPI
url: openapi/increase-entity-onboarding-sessions-api-openapi.yml
- type: Documentation
url: https://increase.com/documentation/api
- aid: increase:increase-entity-supplemental-documents-api
name: Increase Entity Supplemental Documents API
description: The Entity Supplemental Documents API from Increase — 1 operation(s) for entity supplemental documents.
humanURL: https://increase.com/documentation/api
baseURL: https://api.increase.com
tags:
- Entity Supplemental Documents
properties:
- type: OpenAPI
url: openapi/increase-entity-supplemental-documents-api-openapi.yml
- type: Documentation
url: https://increase.com/documentation/api
- aid: increase:increase-event-subscriptions-api
name: Increase Event Subscriptions API
description: Webhooks are event notifications we send to you by HTTPS POST requests. Event Subscriptions are how you configure
your application to listen for them. You can create an Event Subscription through your [developer dashboard](https://dashboard.increase.com/developers/webhooks)
or the API. For more information, see our [webhooks guide](https://increase.com/documentation/webhooks).
humanURL: https://increase.com/documentation/api
baseURL: https://api.increase.com
tags:
- Event Subscriptions
properties:
- type: OpenAPI
url: openapi/increase-event-subscriptions-api-openapi.yml
- type: Documentation
url: https://increase.com/documentation/api
- aid: increase:increase-events-api
name: Increase Events API
description: Events are records of things that happened to objects at Increase. Events are accessible via the List Events
endpoint and can be delivered to your application via webhooks. For more information, see our [webhooks guide](https://increase.com/documentation/webhooks).
humanURL: https://increase.com/documentation/api
baseURL: https://api.increase.com
tags:
- Event
tags_raw:
- Events
properties:
- type: OpenAPI
url: openapi/increase-events-api-openapi.yml
- type: Documentation
url: https://increase.com/documentation/api
- aid: increase:increase-exports-api
name: Increase Exports API
description: Exports are generated files. Some exports can contain a lot of data, like a CSV of your transactions. Others
can be a single document, like a tax form. Since they can take a while, they are generated asynchronously. We send a webhook
when they are ready. For more information, please read our [Exports documentation](https://increase.com/documentation/exports).
humanURL: https://increase.com/documentation/api
baseURL: https://api.increase.com
tags:
- Export
tags_raw:
- Exports
properties:
- type: OpenAPI
url: openapi/increase-exports-api-openapi.yml
- type: Documentation
url: https://increase.com/documentation/api
- aid: increase:increase-external-accounts-api
name: Increase External Accounts API
description: External Accounts represent accounts at financial institutions other than Increase. You can use this API to
store their details for reuse.
humanURL: https://increase.com/documentation/api
baseURL: https://api.increase.com
tags:
- External Accounts
properties:
- type: OpenAPI
url: openapi/increase-external-accounts-api-openapi.yml
- type: Documentation
url: https://increase.com/documentation/api
- aid: increase:increase-fednow-transfers-api
name: Increase Fednow Transfers API
description: The Fednow Transfers API from Increase — 4 operation(s) for fednow transfers.
humanURL: https://increase.com/documentation/api
baseURL: https://api.increase.com
tags:
- Fednow Transfers
properties:
- type: OpenAPI
url: openapi/increase-fednow-transfers-api-openapi.yml
- type: Documentation
url: https://increase.com/documentation/api
- aid: increase:increase-file-links-api
name: Increase File Links API
description: File Links let you generate a URL that can be used to download a File.
humanURL: https://increase.com/documentation/api
baseURL: https://api.increase.com
tags:
- File Links
properties:
- type: OpenAPI
url: openapi/increase-file-links-api-openapi.yml
- type: Documentation
url: https://increase.com/documentation/api
- aid: increase:increase-files-api
name: Increase Files API
description: Files are objects that represent a file hosted on Increase's servers. The file may have been uploaded by you
(for example, when uploading a check image) or it may have been created by Increase (for example, an autogenerated statement
PDF). If you need to download a File, create a File Link.
humanURL: https://increase.com/documentation/api
baseURL: https://api.increase.com
tags:
- File
tags_raw:
- Files
properties:
- type: OpenAPI
url: openapi/increase-files-api-openapi.yml
- type: Documentation
url: https://increase.com/documentation/api
- aid: increase:increase-groups-api
name: Increase Groups API
description: Groups represent organizations using Increase. You can retrieve information about your own organization via
the API. More commonly, OAuth platforms can retrieve information about the organizations that have granted them access.
Learn more about OAuth [here](https://increase.com/documentation/oauth).
humanURL: https://increase.com/documentation/api
baseURL: https://api.increase.com
tags:
- Group
tags_raw:
- Groups
properties:
- type: OpenAPI
url: openapi/increase-groups-api-openapi.yml
- type: Documentation
url: https://increase.com/documentation/api
- aid: increase:increase-inbound-ach-transfers-api
name: Increase Inbound Ach Transfers API
description: The Inbound Ach Transfers API from Increase — 5 operation(s) for inbound ach transfers.
humanURL: https://increase.com/documentation/api
baseURL: https://api.increase.com
tags:
- Inbound Ach Transfers
properties:
- type: OpenAPI
url: openapi/increase-inbound-ach-transfers-api-openapi.yml
- type: Documentation
url: https://increase.com/documentation/api
- aid: increase:increase-inbound-check-deposits-api
name: Increase Inbound Check Deposits API
description: Inbound Check Deposits are records of third-parties attempting to deposit checks against your account.
humanURL: https://increase.com/documentation/api
baseURL: https://api.increase.com
tags:
- Inbound Check Deposits
properties:
- type: OpenAPI
url: openapi/increase-inbound-check-deposits-api-openapi.yml
- type: Documentation
url: https://increase.com/documentation/api
- aid: increase:increase-inbound-fednow-transfers-api
name: Increase Inbound Fednow Transfers API
description: The Inbound Fednow Transfers API from Increase — 2 operation(s) for inbound fednow transfers.
humanURL: https://increase.com/documentation/api
baseURL: https://api.increase.com
tags:
- Inbound Fednow Transfers
properties:
- type: OpenAPI
url: openapi/increase-inbound-fednow-transfers-api-openapi.yml
- type: Documentation
url: https://increase.com/documentation/api
- aid: increase:increase-inbound-mail-items-api
name: Increase Inbound Mail Items API
description: Inbound Mail Items represent pieces of physical mail delivered to a Lockbox Address.
humanURL: https://increase.com/documentation/api
baseURL: https://api.increase.com
tags:
- Inbound Mail Items
properties:
- type: OpenAPI
url: openapi/increase-inbound-mail-items-api-openapi.yml
- type: Documentation
url: https://increase.com/documentation/api
- aid: increase:increase-inbound-real-time-payments-transfers-api
name: Increase Inbound Real Time Payments Transfers API
description: The Inbound Real Time Payments Transfers API from Increase — 2 operation(s) for inbound real time payments
transfers.
humanURL: https://increase.com/documentation/api
baseURL: https://api.increase.com
tags:
- Inbound Real Time Payments Transfers
properties:
- type: OpenAPI
url: openapi/increase-inbound-real-time-payments-transfers-api-openapi.yml
- type: Documentation
url: https://increase.com/documentation/api
- aid: increase:increase-inbound-wire-drawdown-requests-api
name: Increase Inbound Wire Drawdown Requests API
description: Inbound wire drawdown requests are requests from someone else to send them a wire. For more information, see
our [Wire Drawdown Requests documentation](/documentation/wire-drawdown-requests).
humanURL: https://increase.com/documentation/api
baseURL: https://api.increase.com
tags:
- Inbound Wire Drawdown Requests
properties:
- type: OpenAPI
url: openapi/increase-inbound-wire-drawdown-requests-api-openapi.yml
- type: Documentation
url: https://increase.com/documentation/api
- aid: increase:increase-inbound-wire-transfers-api
name: Increase Inbound Wire Transfers API
description: An Inbound Wire Transfer is a wire transfer initiated outside of Increase to your account.
humanURL: https://increase.com/documentation/api
baseURL: https://api.increase.com
tags:
- Inbound Wire Transfers
properties:
- type: OpenAPI
url: openapi/increase-inbound-wire-transfers-api-openapi.yml
- type: Documentation
url: https://increase.com/documentation/api
- aid: increase:increase-intrafi-account-enrollments-api
name: Increase Intrafi Account Enrollments API
description: The Intrafi Account Enrollments API from Increase — 3 operation(s) for intrafi account enrollments.
humanURL: https://increase.com/documentation/api
baseURL: https://api.increase.com
tags:
- Intrafi Account Enrollments
properties:
- type: OpenAPI
url: openapi/increase-intrafi-account-enrollments-api-openapi.yml
- type: Documentation
url: https://increase.com/documentation/api
- aid: increase:increase-intrafi-exclusions-api
name: Increase Intrafi Exclusions API
description: The Intrafi Exclusions API from Increase — 3 operation(s) for intrafi exclusions.
humanURL: https://increase.com/documentation/api
baseURL: https://api.increase.com
tags:
- Intrafi Exclusions
properties:
- type: OpenAPI
url: openapi/increase-intrafi-exclusions-api-openapi.yml
- type: Documentation
url: https://increase.com/documentation/api
- aid: increase:increase-lockbox-addresses-api
name: Increase Lockbox Addresses API
description: Lockbox Addresses are physical locations that can receive mail containing paper checks.
humanURL: https://increase.com/documentation/api
baseURL: https://api.increase.com
tags:
- Lockbox Addresses
properties:
- type: OpenAPI
url: openapi/increase-lockbox-addresses-api-openapi.yml
- type: Documentation
url: https://increase.com/documentation/api
- aid: increase:increase-lockbox-recipients-api
name: Increase Lockbox Recipients API
description: Lockbox Recipients represent an inbox at a Lockbox Address. Checks received for a Lockbox Recipient are deposited
into its associated Account.
humanURL: https://increase.com/documentation/api
baseURL: https://api.increase.com
tags:
- Lockbox Recipients
properties:
- type: OpenAPI
url: openapi/increase-lockbox-recipients-api-openapi.yml
- type: Documentation
url: https://increase.com/documentation/api
- aid: increase:increase-oauth-applications-api
name: Increase Oauth Applications API
description: The Oauth Applications API from Increase — 2 operation(s) for oauth applications.
humanURL: https://increase.com/documentation/api
baseURL: https://api.increase.com
tags:
- OAuth Applications
tags_raw:
- Oauth Applications
properties:
- type: OpenAPI
url: openapi/increase-oauth-applications-api-openapi.yml
- type: Documentation
url: https://increase.com/documentation/api
- aid: increase:increase-oauth-connections-api
name: Increase Oauth Connections API
description: The Oauth Connections API from Increase — 2 operation(s) for oauth connections.
humanURL: https://increase.com/documentation/api
baseURL: https://api.increase.com
tags:
- Oauth Connections
properties:
- type: OpenAPI
url: openapi/increase-oauth-connections-api-openapi.yml
- type: Documentation
url: https://increase.com/documentation/api
- aid: increase:increase-pending-transactions-api
name: Increase Pending Transactions API
description: Pending Transactions are potential future additions and removals of money from your bank account. They impact
your available balance, but not your current balance. To learn more, see [Transactions and Transfers](/documentation/transactions-transfers).
humanURL: https://increase.com/documentation/api
baseURL: https://api.increase.com
tags:
- Pending Transactions
properties:
- type: OpenAPI
url: openapi/increase-pending-transactions-api-openapi.yml
- type: Documentation
url: https://increase.com/documentation/api
- aid: increase:increase-physical-card-profiles-api
name: Increase Physical Card Profiles API
description: This contains artwork and metadata relating to a Physical Card's appearance. For more information, see our
guide on [physical card artwork](https://increase.com/documentation/card-art-physical-cards).
humanURL: https://increase.com/documentation/api
baseURL: https://api.increase.com
tags:
- Physical Card Profiles
properties:
- type: OpenAPI
url: openapi/increase-physical-card-profiles-api-openapi.yml
- type: Documentation
url: https://increase.com/documentation/api
- aid: increase:increase-physical-cards-api
name: Increase Physical Cards API
description: Custom physical Visa cards that are shipped to your customers. The artwork is configurable by a connected [Card
Profile](/documentation/api#card-profiles). The same Card can be used for multiple Physical Cards. Printing cards incurs
a fee. Please contact [support@increase.com](mailto:support@increase.com) for pricing!
humanURL: https://increase.com/documentation/api
baseURL: https://api.increase.com
tags:
- Physical Cards
properties:
- type: OpenAPI
url: openapi/increase-physical-cards-api-openapi.yml
- type: Documentation
url: https://increase.com/documentation/api
- aid: increase:increase-programs-api
name: Increase Programs API
description: Programs determine the compliance and commercial terms of Accounts. By default, you have a Commercial Banking
program for managing your own funds. If you are lending or managing funds on behalf of your customers, or otherwise engaged
in regulated activity, we will work together to create additional Programs for you.
humanURL: https://increase.com/documentation/api
baseURL: https://api.increase.com
tags:
- Programs
properties:
- type: OpenAPI
url: openapi/increase-programs-api-openapi.yml
- type: Documentation
url: https://increase.com/documentation/api
- aid: increase:increase-real-time-decisions-api
name: Increase Real Time Decisions API
description: The Real Time Decisions API from Increase — 2 operation(s) for real time decisions.
humanURL: https://increase.com/documentation/api
baseURL: https://api.increase.com
tags:
- Real Time Decisions
properties:
- type: OpenAPI
url: openapi/increase-real-time-decisions-api-openapi.yml
- type: Documentation
url: https://increase.com/documentation/api
- aid: increase:increase-real-time-payments-transfers-api
name: Increase Real Time Payments Transfers API
description: The Real Time Payments Transfers API from Increase — 4 operation(s) for real time payments transfers.
humanURL: https://increase.com/documentation/api
baseURL: https://api.increase.com
tags:
- Real Time Payments Transfers
properties:
- type: OpenAPI
url: openapi/increase-real-time-payments-transfers-api-openapi.yml
- type: Documentation
url: https://increase.com/documentation/api
- aid: increase:increase-routing-numbers-api
name: Increase Routing Numbers API
description: Routing numbers are used to identify your bank in a financial transaction.
humanURL: https://increase.com/documentation/api
baseURL: https://api.increase.com
tags:
- Routing Numbers
properties:
- type: OpenAPI
url: openapi/increase-routing-numbers-api-openapi.yml
- type: Documentation
url: https://increase.com/documentation/api
- aid: increase:increase-simulations-api
name: Increase Simulations API
description: The Simulations API from Increase — 48 operation(s) for simulations.
humanURL: https://increase.com/documentation/api
baseURL: https://api.increase.com
tags:
- Simulation
tags_raw:
- Simulations
properties:
- type: OpenAPI
url: openapi/increase-simulations-api-openapi.yml
- type: Documentation
url: https://increase.com/documentation/api
- aid: increase:increase-swift-transfers-api
name: Increase Swift Transfers API
description: Swift Transfers send funds internationally.
humanURL: https://increase.com/documentation/api
baseURL: https://api.increase.com
tags:
- Swift Transfers
properties:
- type: OpenAPI
url: openapi/increase-swift-transfers-api-openapi.yml
- type: Documentation
url: https://increase.com/documentation/api
- aid: increase:increase-transactions-api
name: Increase Transactions API
description: Transactions are the immutable additions and removals of money from your bank account. They're the equivalent
of line items on your bank statement. To learn more, see [Transactions and Transfers](/documentation/transactions-transfers).
humanURL: https://increase.com/documentation/api
baseURL: https://api.increase.com
tags:
- Transaction
tags_raw:
- Transactions
properties:
- type: OpenAPI
url: openapi/increase-transactions-api-openapi.yml
- type: Documentation
url: https://increase.com/documentation/api
- aid: increase:increase-wire-drawdown-requests-api
name: Increase Wire Drawdown Requests API
description: Wire drawdown requests enable you to request that someone else send you a wire. Because there is nuance to
making sure your counterparty's bank processes these correctly, we ask that you reach out to [support@increase.com](mailto:support@increase.com)
to enable this feature so we can help you plan your integration. For more information, see our [Wire Drawdown Requests
documentation](/documentation/wire-drawdown-requests).
humanURL: https://increase.com/documentation/api
baseURL: https://api.increase.com
tags:
- Wire Drawdown Requests
properties:
- type: OpenAPI
url: openapi/increase-wire-drawdown-requests-api-openapi.yml
- type: Documentation
url: https://increase.com/documentation/api
- aid: increase:increase-wire-transfers-api
name: Increase Wire Transfers API
description: Wire transfers move funds between your Increase account and any other account accessible by Fedwire.
humanURL: https://increase.com/documentation/api
baseURL: https://api.increase.com
tags:
- Wire Transfers
properties:
- type: OpenAPI
url: openapi/increase-wire-transfers-api-openapi.yml
- type: Documentation
url: https://increase.com/documentation/api
- aid: increase:increase-increase-api-api
name: Increase API
description: The Increase API API from Increase — 0 operation(s) for increase api.
humanURL: https://increase.com/documentation/api
baseURL: https://api.increase.com
tags:
- Increase API
properties:
- type: OpenAPI
url: openapi/increase-increase-api-api-openapi.yml
- aid: increase:increase-oauth-api
name: Increase OAUTH API
description: The Oauth API from Increase — 1 operation(s) for oauth.
humanURL: https://increase.com/documentation/api
baseURL: https://api.increase.com
tags:
- OAuth
- Authentication
tags_raw:
- Oauth
- Authentication
properties:
- type: OpenAPI
url: openapi/increase-oauth-api-openapi.yml
- type: Documentation
url: https://increase.com/documentation/api
common:
- type: Pricing
url: https://increase.com/fees
- type: CapabilityMap
url: capabilities/increase-capability-edges.yml
name: Increase Business Capability Map
- type: Sandbox
url: https://increase.com/documentation/sandbox
# --- truncated at 32 KB (33 KB total) ---
# Full source: https://artifacts.apis.io/increase/apis.yml
Increase API — frequently asked questions
Does Increase have an API?
Yes. APIs.io lists 57 APIs from Increase, including Increase Account Numbers API, Increase Account Statements API and Increase Account Transfers API, and 54 more.
Is there an OpenAPI specification for the Increase API?
Yes. APIs.io indexes 57 OpenAPI specifications for Increase, each linked for download from this page.
How do I authenticate with the Increase API?
Increase uses bearer-token authentication (http · 1 scheme). The details are profiled on APIs.io as Increase Authentication.
How much does the Increase API cost?
Increase publishes its prices; its Same-day ACH origination plan is $2.00/ transaction as of 2026-09-20. APIs.io lists 25 pricing plans for Increase, with each plan's price, limits and inclusions under Pricing on this page.
Is the Increase API ready for AI agents?
Increase has a Kin Score of 48.6 out of 100 (developing) and an Agent Readiness score of 37.1 (agent-ready), scored by API Evangelist on 2026-11-13.
Calls without X-API-Key need no key. Calls with it need a paid plan — get a key.
Get an API key
Free tier, no form to fill in. Signing in shares your email address with us — we
store it to create your key and to recognise you if you sign in with another
provider. See our Privacy Policy and
Terms.
Kin Score
How this is scored →
It updates itself when the score changes. Paste this where you link to your API docs: