Subscribe to a federation directory

POST

/admin/federation/directories

• Local development behind nginx (port 8088 by default)

Fetches /v1/operator from the directory URL, captures the operator pubkey + fingerprint, and persists the subscription. The admin should review the returned fingerprint out-of-band before relying on the directory.

Authorizations

• cookieAuth
• bearerAuth

Request Body ^required

object

directory_url

required

Directory base URL (https, no path, no trailing slash).

string

notes

string

Responses

201

Subscription created.

One subscribed federation directory. Pairing alone shares no content; directories are discovery aids per docs/spec/federation-directory/v1.md.

object

id

required

string format: uuid

directory_url

required

string

operator_name

required

string

operator_public_key

required

PEM-wrapped Ed25519 directory operator pubkey (pinned at subscribe time).

string

operator_fingerprint

required

string

operator_contact

string

subscribed_at

required

string format: date-time

subscribed_by_user_ref

required

integer format: int64

enabled

required

boolean

last_polled_at

string format: date-time

nullable

last_poll_status

required

string

Allowed values: never_polled ok unreachable signature_failed malformed spec_version_mismatch

last_poll_error

required

string

poll_interval_seconds

required

integer

notes

required

string

publish_status

string

Allowed values: not_published pending_dns pending_register listed failed

publish_pending_token

string

publish_token_expires_at

string format: date-time

nullable

publish_record_name

string

publish_record_value

string

publish_listing_id

string

publish_last_attempt_at

string format: date-time

nullable

publish_last_error

string

publish_display_name

string

publish_region

string

publish_description

string

publish_tags

Array<string>

400

Malformed request

object

error

required

Human-readable error summary

string

Example

the request could not be completed

401

Authentication required, missing, or invalid

object

error

required

Human-readable error summary

string

Example

the request could not be completed

Example

{
  "error": "authentication required: sign in and retry with a valid session or API token"
}

403

Authenticated but missing required capabilities

object

error

required

Human-readable error summary

string

Example

the request could not be completed

409

Already subscribed to this directory URL.

object

error

required

Human-readable error summary

string

Example

the request could not be completed