Get linked user vektor

Get Linked User Decryption Vector

This endpoint retrieves the decryption vector associated with a linked user. The vector, combined with an appropriate key, is used to decrypt secure data for the specified user. This endpoint is critical for secure handling of sensitive user data and should be accessed by authorized systems only.

Endpoint

GET /api/auth/linked/secret/{linkedUserId}

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 your system needs to decrypt secured data belonging to a linked user. The returned vector must be combined with the appropriate decryption key held by your system to complete the decryption process. This operation is typically performed as part of a secure data access flow before presenting or processing sensitive linked user information.

Path Parameters

Parameter	Type	Required	Description
linkedUserId	integer (int32)	Yes	The unique identifier of the linked user for whom the decryption vector is being retrieved.

Response

200 OK

Field	Type	Description
token	string	The decryption vector used in conjunction with a key to decrypt secure user data.
expiration	string (date-time)	The expiration date and time of the returned token/vector.
userId	integer (int32)	The unique identifier of the linked user associated with this vector.

{
  "token": "eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9...",
  "expiration": "2026-06-08T14:30:00Z",
  "userId": 10042
}

Error Codes

Code	When it happens
400	Invalid or malformed linkedUserId value supplied
401	Token missing, expired, or invalid
403	Insufficient permissions to access this linked user's secret
404	No linked user found for the specified linkedUserId
500	Internal server error

Common Mistakes

Passing a non-integer value for linkedUserId — the parameter must be a valid int32 integer, not a UUID or string identifier.
Attempting to use the returned token value alone without combining it with the correct decryption key; the vector is only one part of the decryption process.
Not checking the expiration field — the vector may have a limited validity window, after which it cannot be used for decryption.

Related Endpoints

POST /api/auth/v2 — Obtain a Bearer token for authentication
POST /api/auth/refresh — Refresh an existing Bearer token

Example

curl -X GET https://api.banking.netevia.dev/api/auth/linked/secret/10042 \
  -H "Authorization: Bearer YOUR_TOKEN" \
  -H "Content-Type: application/json"