Node line tags node-line-tags
Each primary node picks one access root domain and some of its lines; when setting up resolution, nodes tagged with the current line are preselected.
Pick an endpoint to see its example call on the right.
Authentication
Send the X-API-Key header (create a key on the API Keys page; the key is shown only once at creation). An Authorization: Bearer token obtained by logging in also works.
X-API-Key
Authentication failures return 401; forbidden returns 403 (code such as insufficient_scope).
Conventions
Paging uses page (from 1) and page_size; sort with sort=field or sort=-field.
Times are RFC 3339 (UTC); amounts are in cents.
Writes return 200/201/204 on success; duplicates of a unique key return 409.
/api/v2/node-line-tagsList node line tags
Authentication: Admin only
Node line tags object
| Field | Type | Description |
|---|---|---|
domain | string | Access root domain; empty when there is no tag. |
domain_id | integer | Id of the access root domain the lines come from; 0 = no tag. |
lines | string[] | Unified line codes (deduplicated, in submitted order). |
node_id | integer | Primary node id (sub-IP tags are stored on the primary node). |
Responses and errors
Success returns the resource JSON directly (HTTP 2xx); failures return application/problem+json (code, detail, plus errors on validation failures); lists carry items + total.
{
"id": 1,
"name": "example"
}{
"items": [
{
"id": 1
}
],
"page": 1,
"page_size": 20,
"total": 1
}{
"code": "validation_failed",
"detail": "Invalid request parameters",
"errors": [
{
"code": "required",
"field": "/name",
"message": "name is required"
}
],
"request_id": "0123456789abcdef",
"status": 422,
"title": "Unprocessable Entity",
"type": "about:blank"
}