Complete a move

At the new address, signed by the move's key, with the secret: the kept version is published through the same path as a card's next version. A second call gets the same answer.

POST/v1/moves/{nonce}/complete

Access: Signed request
Client: Local or server client

Parameters#

Name	Location	Meaning
`nonce`Required	Path	The move's nonce: 22 characters of base64url.

JSON body#

Name	Location	Meaning
`secret`Required	JSON	The move's 32-byte secret in base64url, which the old page handed to this one.

This call also needs the common signed-request headers, nonce and timestamp. Prepare and sign request.json before using the example. Request signing

Request examples#

cURL

curl -fsS -X POST 'https://veil.pub/v1/moves/MOVE_NONCE/complete' \
  -H "X-Public-Key: $NEW_KEY" -H "X-Signature: $REQUEST_SIGNATURE" --json @complete.json

Response#

HTTP 201application/json

201 with identity, version, url, logIndex, publishedAt, checkpoint, receipt and receiptSignature; 200 with the same and again true afterwards.

Field	Type	Meaning
`identity`	`integer`	The card's number.
`version`	`integer`	The version that added the key.
`logIndex`	`integer`	Its entry in the log.
`receipt`	`string`	The receipt the old key signed.

Response headers#

Header	Value	Meaning
`Content-Type`	`application/json`	Use the declared media type before choosing a parser.
`Date`	`HTTP date`	Server time. Compare it with your clock when signing requests.
`Cache-Control`	`no-store`	Do not persist private or temporary responses in a shared cache.
`Retry-After`	`integer seconds, on rate_limited or busy`	Wait at least this long before retrying. Other 429/503 codes do not necessarily include it.

Usage notes#

Moving a browser from the directory's old address to its new one (since 6 November 2026): a key lives on the origin that made it, so the new address makes a key of its own and the card adds it with a version signed at the old address, in the same browser. The version is kept until the new key comes back with the secret.

Errors#

API errors return an error object. Use error.code for program logic; error.message is English text for people and can change. Response and error guide

HTTP	Code	Meaning and next step
400	`invalid_json`	The body is not a JSON object, contains duplicate keys or has trailing data. Send one valid JSON object with `Content-Type` application/json.
400	`invalid_nonce`	The signed-request nonce has an invalid format. Generate a fresh 16 to 128-character nonce using letters, digits, _ or -.
400	`invalid_parameter`	A path, query or body field is missing, malformed or outside its accepted range. Correct the field named in `error.message` before sending again.
400	`invalid_signature_alg`	`X-Signature-Alg` is unsupported. Use a supported signing algorithm and matching key/signature encoding.
400	`invalid_timestamp`	The signed-request timestamp is not Unix milliseconds. Use an integer Unix timestamp in milliseconds and sign the corrected request.
400	`wrong_format`	The request or the read belongs to the other log format than this server’s: a v1 record on a format 2 log, or a format 2 read on a format 1 log. Read `format` in GET /v1/log (absent means 1) and send the shape of that format.
401	`invalid_signature`	The HTTP request signature does not verify. Sign the exact method, path and body bytes, without changing them afterwards.
401	`missing_signature`	The request requires a device signature and its headers are missing or unreadable. Send `X-Public-Key`, `X-Signature` and the signed-request metadata. An API key does not replace a device signature.
401	`stale_timestamp`	The signed timestamp is outside the accepted clock window. Compare the server Date header with your clock, then generate a fresh nonce, timestamp and signature.
403	`key_banned`	The device signing key is suspended by Veil staff. Use an authorised active key or ask staff to review the restriction.
403	`move_forbidden`	The move is not the caller's to complete: another key signs, the secret is not the move's, or the old page has not approved it yet. The three get the same answer. Complete a move only from the browser that started it, with the secret its approval returned.
404	`no_move`	This directory has one address, so there is no browser to move. Make a card or log in at this address.
404	`not_found`	The requested card, key, alias, code or resource was not found. Check the identifier. Temporary codes and previews may already have expired or been used.
409	`replayed_nonce`	The signing key already used this nonce. Check whether the previous request succeeded before making a fresh signed request.
409	`version_conflict`	The version cannot be published against the card’s current state. Read the latest card, reconcile the intended change and sign a new version.
410	`move_expired`	The move waited more than ten minutes. Start a new move.
413	`payload_too_large`	The request body exceeds this endpoint’s byte limit. Reduce the encoded body. API-key management accepts at most 8 KiB.
429	`rate_limited`	An anonymous, signed-request or API-key allowance was exceeded. Wait at least `Retry-After` seconds. Share a queue and retry budget across your workers.
500	`internal_error`	An unexpected server error occurred. Internal details are not returned. Retry reads with bounded backoff. Check write results before sending a new signed operation.
503	`busy`	The application has reached a temporary concurrency or database limit. Wait `Retry-After` seconds and retry with bounded backoff.

Read this entry as JSON