Submit /v1/register with the previously-issued token
POST /admin/federation/directories/{id}/publish/register
Persists the operator-supplied display_name + region +
description + tags, then POSTs /v1/register with the
pending token. Caller MUST have completed the DNS step.
On success flips status to listed; on failure stays
pending_dns so the operator can retry once DNS
propagates.
Authorizations
Section titled “Authorizations ”Parameters
Section titled “ Parameters ”Path Parameters
Section titled “Path Parameters ”Request Body required
Section titled “Request Body required ”Operator-chosen entry metadata for /v1/register. Saved on the directory row so it pre-fills the form next time.
object
Responses
Section titled “ Responses ”Result of the register call.
One subscribed federation directory. Pairing alone shares no content; directories are discovery aids per docs/spec/federation-directory/v1.md.
object
PEM-wrapped Ed25519 directory operator pubkey (pinned at subscribe time).
Malformed request
object
Human-readable error summary
Example
the request could not be completedAuthentication required, missing, or invalid
object
Human-readable error summary
Example
the request could not be completedExample
{ "error": "authentication required: sign in and retry with a valid session or API token"}Authenticated but missing required capabilities
object
Human-readable error summary
Example
the request could not be completedResource not found
object
Human-readable error summary
Example
the request could not be completed