space.highport.manage.enableDelegation

Make a registered domain a delegation base, so its owner can reserve names directly under it for other identities. Returns the wildcard record that routes those names. The caller must own the base, and it must be verified or active.

Details · procedure
Kindprocedure
Authoritymanage.highport.space
Indexed

Procedure

procedure · POST

Input

application/json

domain

requiredstring

The base: a domain registered to the caller.

  • maxLength: 253

maxNames

integer

The most names the base can reserve. Defaults to the deployment's setting; a value above the deployment's ceiling is refused.

  • minimum: 1

Output

application/json

domain

requiredstring

A random name under the base, used to prove the wildcard routes. Absent while the base has no probe.

  • maxLength: 253

records

requiredarray

The DNS records to publish: the wildcard traffic record.

Errors

InvalidDomain

Not a syntactically valid domain.

NotBaseOwner

No verified or active registration of that domain belongs to the caller.

DelegationUnsupported

This domain cannot be a delegation base. It is registered to a space, is a domain this deployment provides or a name under one, was itself handed out under a base, or sits above or below a domain with delegation turned on. Bases do not nest.

MaxNamesAboveLimit

maxNames is above this deployment's per-base limit.

CaaForbidsIssuance

The base's CAA records do not allow this deployment's certificate issuer, account, or challenge method. The error message names the blocking record.

Similar lexicons

semantic match

Lexicons whose schemas describe something close to this one. Check them before publishing a new one that overlaps.

  • Choose how names under a proven base get certificates. wildcard lets this service get one wildcard certificate for the base over DNS-01, through the base's own challenge target, and returns the record that delegates it. per-name ends that grant. The caller must own the base, which must be verified or active. Delegation does not need to be enabled.

  • Reserve a name directly under a delegation base for another identity. The name answers /.well-known/atproto-did with the subject right away, and the subject can then publish a site there. The caller must own the base. Any unproven claim on the name is replaced. Repeating the call for the same subject returns the existing reservation and does not count against maxNames. Reservations last as long as the base.

  • Register a domain to the caller, or to a space the caller is the authority of, and get the DNS records needed to prove ownership and route traffic.

  • Stop a base handing out names: remove its probe and clear its delegation state. Refused while any reservation remains; release each one with releaseReservation. A certificate grant on the base is left in place.

  • Release a domain: deactivate its site and stop authorizing it for TLS. Certificates already issued for it stay valid until they expire. If the domain is a base with a wildcard grant, the grant ends and the wildcard is revoked and deleted; no account can take the domain until that finishes. Stored blobs are left for garbage collection.