Skip to main content
GET
/
admin
/
api
/
v1
/
Integrations
List integrations available to the calling client.
curl --request GET \
  --url https://admin-api.meshconnect.com/admin/api/v1/Integrations \
  --header 'Authorization: Bearer <token>'
{
  "message": "<string>",
  "displayMessage": "<string>",
  "errorHash": "<string>",
  "teamCode": "<string>",
  "errorType": "<string>",
  "errorData": null,
  "content": {
    "items": [
      {
        "id": "3c90c3cc-0d44-4b50-8888-8dd25736052a",
        "name": "<string>",
        "category": "<string>"
      }
    ]
  }
}

Authorizations

​
Authorization
string
header
required

Authorization header using the Bearer scheme. Example: "Authorization: Bearer {Value}"

Response

Integrations returned

​
status
enum<string>
Available options:
ok,
serverFailure,
permissionDenied,
badRequest,
notFound,
conflict,
tooManyRequest,
locked,
unavailableForLegalReasons
​
message
string | null

A message generated by the API

​
displayMessage
string | null

User-friendly display message that can be presented to the end user

​
errorHash
string | null
read-only

An error grouping hash from string components and caller information. Used by bugsnag on FE for correct error grouping

​
teamCode
string | null
read-only

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 | null

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
object

The list of integrations surfaced to a client's admin picker, as returned by GET /admin/api/v1/integrations. This is a CURATED picker list, NOT an authoritative universe of acceptable ids — DeFiWallet-only parent Org.Front.Core.Contracts.Adapters.Persistence.Entities.FinancialInstitution rows are deduplicated out (their child Org.Front.Core.Contracts.Adapters.Persistence.Entities.DeFiWallet rows are surfaced instead), and unavailable brokers may be filtered. Catalog validation elsewhere still accepts any persisted id, so callers that source ids outside this picker (Retool back-fill, migrations, etc.) won't see a validation failure for an id absent here. Full broker metadata lives behind the Link SDK catalog API (IIntegrationsQueryService) which is end-user contextual; this surface is admin-side.