GET /v2/core_accounts and GET /v2/core_accounts/{id}.
Fields
Account types
attributed. An FBO whose funds are fully attributed to end customers. Each customer’s share is a user balance beneath this account. Most consumer deposit programs have one of these.direct. Everything else your program runs on: operating, settlement, revenue, and reserve DDAs, and any FBO that is not attributed at the customer level. Account numbers can attach directly to a direct account’s balance, so payments can route to it.shadow. A sweep or placement position, such as IntraFi ICS, that mirrors funds held elsewhere. You can read its balance. Nothing transacts against it directly and account numbers never attach.
The entities block
The entities referenced here are
lead or partner type entities that Lead provisions during onboarding. They appear on GET /v0/entities as read-only records and cannot be created or updated by you. See Entity.
Allowed actors
Some Lead-held accounts need a partner-owned account number, for example an FBO that Lead holds but that your treasury team needs to route into.allowed_actors lists the entity IDs that may hold account numbers on this account even though they are not account holders.
Under Account Number V2, an account number’s entity_id must be either an account holder on the parent core account or an entry in allowed_actors. On v1, allowed_actors is informational and nothing is enforced against it.
List and retrieve
GET /v2/core_accounts returns every core account visible to your program. Filters:
type. One ofattributed,direct,shadow.limit,starting_after,ending_before. Cursor pagination. Cursors are core account IDs.
GET /v2/core_accounts/{id} returns one account. Returns 404 if the ID does not exist or belongs to another program.
Neither endpoint triggers webhooks or business validations. Errors are the standard set on the Errors page.

