Skip to main content
Submit Application authorization
First prepare the authorization. Submit the same action fields and current nonce with signatures over the decoded canonical_payload bytes.

Request

string
required
Registered Application ID.
string
required
set_domain or set_linked_did, exactly as prepared.
string
required
Control DID key used to sign the prepared payload.
integer
required
Current nonce returned by preparation.
string
required
Exact prepared 0x-prefixed hexadecimal value.
string
required
Base64-encoded 64-byte Ed25519 signature from the control DID key.
For set_domain, repeat domain. For set_linked_did, repeat linked_did, linked_signer_key_id, and Boolean enabled, and include linked_signature: a Base64-encoded 64-byte signature from that DID’s key over the same prepared payload. The 202 response contains application_id, status: "accepted", and tx_hash. Read the Application record after finalization to verify domain or linked_dids. A changed nonce or payload returns 409 application_proof_stale; prepare and sign again. The control action may still fail later if DNS proof, target DID, or service authorization has changed.

Straight to the point