Custodians

The custodian catalogue lists every bank, broker, fund administrator, and platform Aleta can ingest data from. You'll browse this list when onboarding a client, pick the right provider for each depository, and then walk the user through the matching auth flow.

Data model

  • Name
    id
    Type
    string
    Description

    Stable slug for the custodian. Stable across releases — safe to reference from application code.

  • Name
    name
    Type
    string
    Description

    Display name of the custodian.

  • Name
    country
    Type
    ISO 3166-1 alpha-2
    Description

    Home jurisdiction of the custodian's entity that the client is contracting with. One branded custodian can have multiple entries when it operates through more than one legal vehicle (e.g. the same group's Luxembourg and Swiss entities).

  • Name
    supported_auth_flows
    Type
    array of strings
    Description

    IDs of the auth flows that work against this custodian. Clients pick one at onboarding.

  • Name
    data_freshness
    Type
    enum
    Description

    daily, intraday, on_demand. Expected SLA for new activity arriving from this custodian.

GET/v2/custodians

List supported custodians

No scoping or filters — the catalogue is global and small enough to render in a single request. Cache client-side during onboarding flows; the list is stable between releases.

Request

GET
/v2/custodians
curl https://api.aleta.io/v2/custodians \
  -H "Authorization: Bearer {token}"
  • Auth flows — the procedures that link a depository to a custodian.
  • Authorities — the consent records that result from an auth flow.