JustiFi Sub Accounts API
Sub Accounts are the representation of your platform's customers for payment processing in JustiFi and are associated with your platform account.To gain approval for payment processing each of your customers need to be onboarded as a business via [web compoenent](https://docs.justifi.tech/api-spec#tag/Onboarding-via-Component), [hosted onboarding](https://docs.justifi.tech/api-spec#tag/Hosted-Onboarding) or [API](https://docs.justifi.tech/api-spec#tag/Onboarding-via-API).During the onboarding process a sub account is automatically created for each business and updated along the way.Payments can be processed through a sub account once it's status is `enabled`.| Status | Description || ----------- | ----------- || created | this sub account has been created (via Sub Accounts API), but we haven't received their onboarding entry yet || submitted | we've received this sub account's onboarding entry (via hosted onboarding or API) and we're reviewing their information || information_needed | we reviewed this sub account's onboarding entry and found an issue; we need more information before we can enable this account || enabled | this sub account is approved to process payments _note: test accounts are automatically enabled_ || rejected | this sub account didn't pass approval, so they won't be able to process payments || disabled | this sub account was previously approved, but has since become ineligible to process payments (e.g. due to fraud) || archived | this sub account has been archived; they won't be able to process payments (but their record will remain for historical reasons) |
JustiFi Sub Accounts API is one of 28 APIs that JustiFi publishes on the APIs.io network, described by a machine-readable OpenAPI specification.
Tagged areas include Subaccounts. The published artifact set on APIs.io includes an OpenAPI specification and authentication docs.
This API exposes 5 operations across 4 paths, and defines 6 schemas. It is described by OpenAPI 3.2.0.
Requests are made against a single base URL, https://api.justifi.ai/v1.
Metadata
The identity and technical contract details declared by the specification.
Paths & Operations 5
Across 4 paths, the API surfaces 5 operations — 4 GET, 1 POST. Each is listed below with its method, path, parameters, and response codes.
Sub Accounts are the representation of your platform's customers for payment processing in JustiFi and are associated with your platform account. To gain approval for payment proc…
Schemas 6
The contract defines 6 schemas that model the data the API accepts and returns. The most detailed are SubAccount (15 properties), PayoutBankAccount (9 properties), Envelope (4 properties), Envelope-list (4 properties). Each schema is shown below with its type and property counts.
Specification
The full machine-readable OpenAPI contract behind this narrative.
Source
More from JustiFi 12
Other APIs JustiFi publishes across the network.
This is an independent, third-party profile of JustiFi Sub Accounts 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.