Skip to content

Get a config version

GET
/v1/ns/{nsid}/config/{version}
curl --request GET \
--url 'https://example.com/v1/ns/2489E9AD-2EE2-8E00-8EC9-32D5F69181C0/config/example?view=user' \
--header 'Authorization: Bearer <token>'

Returns bare YAML by default. Send Accept: application/json+yaml for a JSON envelope with metadata.

?view=effective returns the post-inheritance merged document — the same version with every section inherited from parent namespaces resolved in, i.e. what the switch actually runs. ?view=user (the default) returns the author-written YAML. In the JSON envelope the effective body arrives in effective_config_yaml; the bare-YAML response returns whichever body matches the view.

nsid
required
string format: uuid

Namespace UUID

version
required
string

Config version: ULID, ‘latest’, ‘running’, or a tag name

view
string
default: user
Allowed values: user effective

Which rendering to return: user (author’s YAML, default) or effective (post-merge document the switch runs).

OK

string

Error response

Media typeapplication/problem+json

RFC 7807 Problem Details

object
type

Problem type slug URI

string
title
string
status
integer
detail
string
key
additional properties
any
Examplegenerated
{
"type": "example",
"title": "example",
"status": 1,
"detail": "example"
}