---
title: "Get all Registered clients"
method: GET
path: "/admin/api/v1/SubClient"
tags: ["Registered Clients"]
---

# Get all Registered clients

`GET /admin/api/v1/SubClient`

Get information about all Registered clients.

## Response `200`

List registered clients

- B2B2BRegisteredClientDataIReadOnlyCollectionApiResult
  - `status` 'ok' | 'serverFailure' | 'permissionDenied' | 'badRequest' | 'notFound' | 'conflict' | 'tooManyRequest' | 'locked' | 'unavailableForLegalReasons'
  - `message` string, nullable — A message generated by the API
  - `displayMessage` string, nullable — User-friendly display message that can be presented to the end user
  - `errorHash` string, nullable — An error grouping hash from string components and caller information. Used by bugsnag on FE for correct error grouping
  - `teamCode` string, nullable — Opaque team code for error routing. Resolved from exception origin or caller file path via CODEOWNERS. Format: 2-character code (e.g., "7K", "M2"). Use for alerting/routing, not display.
  - `errorType` string, nullable — Strictly-typed error type that is explaining the reason of an unsuccessful status of the operation. All possible error types are available in the documentation.
  - `errorData` unknown
  - `content` B2B2BRegisteredClientData[], nullable
    - `businessLegalName` string, required — Registered client Business Legal Name
    - `displayName` string, required — Registered client Display Name
    - `callbackUrls` string[], nullable — Registered client Allowed Link URLs. If no Allowed Link URLs are specified, Allowed Link URLs from main client will be used.
    - `catalogConfiguration` CatalogConfiguration — Catalog configuration for a profile. By default all integrations show; the fields below curate the catalog. integrationWhiteList cannot be combined with excludeIntegrationCategories or excludeIntegrations.
      - `excludeIntegrationCategories` string[], nullable — Entire categories to hide. Allowed values: "exchange", "wallet". Cannot contain both. Applied at catalog-resolution time on top of any GUID-level Org.Front.Core.Contracts.Models.ClientConfigurations.CatalogConfiguration.ExcludeIntegrations filtering (PRG-2793). Mutually exclusive with Org.Front.Core.Contracts.Models.ClientConfigurations.CatalogConfiguration.IntegrationWhiteList — the whitelist mode and category exclusions cannot be combined; the validator rejects payloads that try to set both.
      - `excludeIntegrations` string[], nullable — A blacklist of integration identifiers to hide. Cannot be combined with integrationWhiteList.
      - `integrationWhiteList` string[], nullable — An allow list of integration identifiers — only these show. Cannot be combined with excludeIntegrationCategories or excludeIntegrations.
    - `id` string, uuid — Registered client Id
    - `logoUrl` string, required — Registered client Logo URL address
    - `fundingTokenWhitelist` string[], nullable — Funding token whitelist inherited from the parent (main) client. Read-only — sub-client level funding token whitelisting is tracked under PRG-2682 / Lane C-3.

## Other responses

- `401` — Unauthorized: Auth token request is not valid
- `403` — Permission denied: Request is not allowed

---

[API](https://skmtc.dev/meshconnect/apis/admin-api.md) · [All operations](https://skmtc.dev/meshconnect/apis/admin-api/llms.txt) · [OpenAPI document](https://skmtc-service-production.skmtc.workers.dev/v1/apis/meshconnect/admin-api/revisions/9beb45cfe6f6/schema)