Developers › API reference › User-defined fields
GET /api/v1/udf/{table}/records/{key}
The user-defined values of one record.
- Scope
reference:read - ETag
- operationId
referenceUdfValues
The token needs the scope reference:read, and the person or service account behind it needs the matching privileges and account permissions, exactly as on the screens. See Scopes.
ETag. The answer carries an ETag header. Keep it: changing this resource needs If-Match with that value.
Request
GET /api/v1/udf/{table}/records/{key}
Path parameters
| Name | Description | Example |
|---|---|---|
table | The reference table: securities, issuers, accounts, account_groups, brokers, models, benchmarks, desks or list_entries. | securities |
key | The record's key (a symbol, an account code…). | AAPL |
Headers
| Header | Required | Value |
|---|---|---|
Authorization | yes | Bearer <token>: an OAuth access token (vat_…) or a personal access token (vpt_…). Get a token |
Examples
Keep the token in an environment variable (VESTORIS_TOKEN), never in the script.
curl
curl "https://vestoris.com/api/v1/udf/securities/records/AAPL" \
-H "Authorization: Bearer $VESTORIS_TOKEN"
Python (requests)
import os, requests
r = requests.get(
"https://vestoris.com/api/v1/udf/securities/records/AAPL",
headers={
"Authorization": f"Bearer {os.environ['VESTORIS_TOKEN']}",
},
timeout=30,
)
r.raise_for_status() # errors are application/problem+json with a stable "code"
print(r.json())
JavaScript (fetch)
const res = await fetch("https://vestoris.com/api/v1/udf/securities/records/AAPL", {
method: "GET",
headers: {
Authorization: `Bearer ${process.env.VESTORIS_TOKEN}`,
},
});
const data = await res.json();
if (!res.ok) throw new Error(`${data.code}: ${data.detail}`); // problem+json
console.log(data);
Response
200 OK, application/json: UdfValues. With an ETag header. Rate-limit headers: RateLimit-Limit, RateLimit-Remaining, RateLimit-Reset.
Response fields
| Field | Type | Description |
|---|---|---|
table | string | The reference table: securities, issuers, accounts, account_groups, brokers, models, benchmarks, desks, list_entries. |
key | string | The record's natural key (e.g. a symbol or account code). |
values | object | Values by field name. |
Example response
HTTP/1.1 200 OK
Content-Type: application/json
ETag: "3f1a9c0e5b7d2a4c8e6f0b1d3a5c7e9f"
{
"table": "securities",
"key": "AAPL",
"values": {
"Internal rating": "BB"
}
}
Example values. Your values depend on your firm's data; prices, orders and fills are simulated.
Status codes and errors
Errors are application/problem+json (RFC 9457) with a stable code to program against; the detail says what to fix. See Errors.
| Status | When | Problem codes |
|---|---|---|
| 200 | Success | |
| 400 | The request is malformed | invalid_request |
| 401 | No token, or it is invalid or expired | invalid_token |
| 403 | The token lacks the scope, or the person or service account behind it lacks the privilege or account permission | insufficient_scope forbidden ip_not_allowed |
| 404 | Not found, or not visible to you (the API never confirms what you may not see) | not_found |
| 429 | Rate limited: wait for Retry-After seconds | rate_limited |
{
"type": "https://vestoris.com/developers/errors#validation_failed",
"title": "Validation failed",
"status": 422,
"detail": "Quantity must be greater than zero.",
"code": "validation_failed",
"instance": "/api/v1/udf/securities/records/AAPL"
}
On the screens
The same thing in the app is explained in: