Get Linked Accounts

This endpoint is called using the bank customer's credentials and returns all of that customer's requests to link external accounts. Each item in the response array describes one connection request, including the remote account holder's identity, the account type, and the current request status.

Endpoint

GET /api/LinkedAccount

Authentication

Bearer token required. Obtain via:

POST https://api.banking.netevia.dev/api/auth/v2

Include in header: Authorization: Bearer {token}
Token lifetime: 10 minutes. Refresh via POST /api/auth/refresh.

When to use

Use this endpoint when you need to display or audit all linked-account connection requests that belong to the currently authenticated customer. It is useful for onboarding flows where you want to show pending approvals, or for account-management screens that list confirmed external account links.

Response

200 OK

Returns an array of linked account request objects.

[
  {
    "id": 101,
    "fromUserId": 5021,
    "toUserId": 5087,
    "profileId": 312,
    "nickName": "john_bizz",
    "firstName": "John",
    "lastName": "Smith",
    "dba": "Smith Enterprises",
    "isSubUser": false,
    "accepted": true,
    "type": 2,
    "status": "APPROVED",
    "createdDate": "2024-09-12T09:48:50.532Z"
  },
  {
    "id": 102,
    "fromUserId": 5021,
    "toUserId": 5099,
    "profileId": 315,
    "nickName": "jane_consumer",
    "firstName": "Jane",
    "lastName": "Doe",
    "dba": null,
    "isSubUser": false,
    "accepted": false,
    "type": 1,
    "status": "PENDING",
    "createdDate": "2024-10-01T14:22:10.000Z"
  }
]

Error Codes

Common Mistakes

• Calling this endpoint with a partner-level or admin token instead of the bank customer's own Bearer token — the response is scoped to the authenticated customer, so using the wrong credential returns an empty list or a 401.
• Treating accepted: true as equivalent to status: "APPROVED" — these fields are related but set independently; always check status for the canonical approval state.
• Ignoring isSubUser when displaying results — sub-user linked accounts may have a dba value and behave differently from primary business or consumer accounts.
• Not handling null values on nullable fields (nickName, firstName, lastName, dba, status) before rendering them in a UI.

Related Endpoints

• POST /api/LinkedAccount — Create a new linked account connection request
• DELETE /api/LinkedAccount/{id} — Remove an existing linked account connection request
• GET /api/FinancialAccount — List the customer's own financial accounts

Example

curl -X GET https://api.banking.netevia.dev/api/LinkedAccount \
  -H "Authorization: Bearer YOUR_TOKEN" \
  -H "Accept: application/json"