Access requests

Access Requests

This endpoint returns a list of linked account access requests associated with the authenticated user. Each entry represents a request to link accounts between two users on the Netevia platform, and includes information about the requester, recipient, acceptance status, and account type. Use this endpoint to display incoming or outgoing link requests and to drive approval or rejection workflows.

Endpoint

GET /api/LinkedAccount/requests

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 building a UI or workflow that shows users their pending linked account requests — for example, a notifications panel or an account-linking management page. It is also useful during onboarding flows where a business customer needs to review and accept links from authorized users or other Netevia customers. Call this endpoint before presenting accept/reject actions to ensure the request list is current.

Response

200 OK

Returns an array of linked account request objects.

FieldTypeDescription
idinteger (int32)Unique identifier of the linked account request
fromUserIdinteger (int32)ID of the user who initiated the link request
toUserIdinteger (int32)ID of the user who received the link request
profileIdinteger (int32)Profile ID associated with the linked account
dbastring / nullDoing-business-as name of the requester, if applicable
nickNamestring / nullNickname assigned to the linked account
firstNamestring / nullFirst name of the requesting user
lastNamestring / nullLast name of the requesting user
isSubUserbooleanIndicates whether the requesting user is an authorized (sub) user
acceptedbooleanWhether the link request has been accepted (true) or is still pending/declined (false)
createdDatestring (date-time)ISO 8601 timestamp when the request was created
typeinteger (enum)User type code: 1 = Personal, 2 = Business, 3 = SubUser, 4 = Partner, 5 = Admin
statusstring / nullCurrent status of the request (e.g., "Pending", "Accepted", "Declined")
[
  {
    "id": 1042,
    "fromUserId": 3081,
    "toUserId": 4217,
    "profileId": 2205,
    "dba": "Acme Supplies LLC",
    "nickName": "Acme Account",
    "firstName": "Jane",
    "lastName": "Smith",
    "isSubUser": false,
    "accepted": false,
    "createdDate": "2025-11-14T09:32:00Z",
    "type": 2,
    "status": "Pending"
  },
  {
    "id": 1043,
    "fromUserId": 3082,
    "toUserId": 4217,
    "profileId": 2206,
    "dba": null,
    "nickName": "Personal Link",
    "firstName": "John",
    "lastName": "Doe",
    "isSubUser": true,
    "accepted": true,
    "createdDate": "2025-10-05T14:15:00Z",
    "type": 1,
    "status": "Accepted"
  }
]

Error Codes

CodeWhen it happens
401Token missing, expired, or invalid
403Insufficient permissions to view linked account requests
500Internal server error

Common Mistakes

  • Calling this endpoint without a valid Bearer token will return 401; ensure the token is refreshed before it expires (10-minute lifetime).
  • The type field is a numeric enum — do not treat it as a string. Map values (1–5) to user type labels in your application layer.
  • The accepted boolean alone does not reflect all states; always check the status field to distinguish between pending, accepted, and declined requests.
  • This endpoint returns all requests (both incoming and outgoing for the authenticated user); filter by fromUserId or toUserId in your application to separate them.

Related Endpoints

  • POST /api/LinkedAccount/request — Send a new linked account request to another Netevia user
  • POST /api/LinkedAccount/accept — Accept a pending linked account request
  • POST /api/LinkedAccount/decline — Decline a pending linked account request
  • GET /api/LinkedAccount — Retrieve currently active linked accounts

Example

curl -X GET https://api.banking.netevia.dev/api/LinkedAccount/requests \
  -H "Authorization: Bearer YOUR_TOKEN" \
  -H "Accept: application/json"
Headers
string
enum
Defaults to application/json

Generated from available response content types

Allowed:
Response

Language
Credentials
Bearer
JWT
LoadingLoading…
Response
Click Try It! to start a request and see the response here! Or choose an example:
text/plain
application/json
text/json