curl --request POST \
--url "https://directory.example.com/personas/example.com/dns-challenges" \
--header "Content-Type: application/json" \
--data '{
"operator_did": "did:openpayload:1111111111111111111111",
"action": "register_persona"
}'
Personas
Create a Persona DNS challenge
Request the TXT record needed to prove control of a Persona domain
curl --request POST \
--url "https://directory.example.com/personas/example.com/dns-challenges" \
--header "Content-Type: application/json" \
--data '{
"operator_did": "did:openpayload:1111111111111111111111",
"action": "register_persona"
}'
The DNSSEC proof model requires runtime spec 126 or newer and a matching OpenDispatch release. It is available on the alpha network, which currently runs spec 128 / transaction version 6. Domain Personas require a DNSSEC-signed TXT record and a valid delegation chain to an accepted DNS root trust anchor. Unsigned DNS and Directory attestations cannot complete this flow.
409 persona_conflict; a renewal requires the currently registered operator DID.
Request
A DNS name, URL-encoded when necessary. The Directory returns its canonical lowercase ASCII IDNA form.
curl --request POST \
--url "https://directory.example.com/personas/example.com/dns-challenges" \
--header "Content-Type: application/json" \
--data '{
"operator_did": "did:openpayload:1111111111111111111111",
"action": "register_persona"
}'
Response
201 Response
{
"challenge_id": "<challenge-id>",
"persona": "example.com",
"operator_did": "did:openpayload:1111111111111111111111",
"action": "register_persona",
"challenge_nonce": "0",
"operator_nonce": "0",
"record_name": "_openpayload-persona.example.com",
"record_type": "TXT",
"record_value": "openpayload-persona-dnssec-v1=<request-bound-challenge>",
"expires_at": "2026-09-19T12:00:00Z"
}
directory_url, the issuing Directory origin. Use that origin for verification and submission when resuming through a shared Directory hostname.
Publish record_value exactly at record_name. DNS responses can be cached, so wait for propagation before submitting the Persona update.
Straight to the point
POST /personas/{persona}/dns-challenges
- Does not register the Persona
- Challenge is bound to the action, Persona, operator DID, network, and nonce
- Challenge is single-use and expires after 48 hours at
expires_at

