Retrieving Connection Requests

This endpoint returns a list of all connection requests made by accounts associated with a specified banking profile, including both primary and sub-accounts. It is used to inspect which remote accounts have been requested for linking. A security check is enforced to ensure that only the API-User associated with the profile can access its connection requests.

Endpoint

GET /api/LinkedAccount/{id}

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 audit or display the external account linking activity for a customer profile. It is useful for partner dashboards that show pending or accepted connection requests, and for verifying the status of linked external accounts before initiating transfers.

Path Parameters

Response

200 OK

Returns an array of connection request objects. Each object has the following fields:

[
  {
    "id": 1042,
    "fromUserId": 3011,
    "toUserId": 3087,
    "profileId": 8821,
    "dba": "Acme Retail LLC",
    "nickName": "Main Checking",
    "firstName": "Jane",
    "lastName": "Smith",
    "isSubUser": false,
    "accepted": true,
    "createdDate": "2025-03-15T10:22:00Z",
    "type": 2,
    "status": "Active"
  },
  {
    "id": 1043,
    "fromUserId": 3011,
    "toUserId": 3099,
    "profileId": 8821,
    "dba": null,
    "nickName": "Savings",
    "firstName": "John",
    "lastName": "Doe",
    "isSubUser": true,
    "accepted": false,
    "createdDate": "2025-04-01T08:45:00Z",
    "type": 1,
    "status": "Pending"
  }
]

Error Codes

Common Mistakes

• Providing a non-integer value for the id path parameter — the schema requires a 32-bit integer.
• Attempting to retrieve connection requests for a profile that belongs to a different partner — the security check will return 403.
• Confusing the profile id with a user ID or account ID; the id must reference a valid banking profile.
• Not handling a null response for nullable fields such as dba, nickName, firstName, lastName, and status when parsing the response.

Related Endpoints

• POST /api/LinkedAccount — Create a new connection request to link an external account to a banking profile.
• DELETE /api/LinkedAccount/{id} — Remove an existing linked account connection request.
• GET /api/LinkedAccount — Retrieve all linked account connection requests (if available without a profile filter).

Example

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