Submissions

Re-issue a lost ownership token for an update request (F10)

The ownership token is returned exactly once, by request-update. If it is lost, this endpoint queues a replacement: POST the request_id together with the SAME email that created the request. The new token is delivered BY EMAIL ONLY, to the address already on the request, and never appears in this response. The response is deliberately identical in every case (request found or not, wrong email, already verified, already reviewed, token expired, re-issue already queued): this endpoint is not an oracle for whether a pending update request exists, which is information x402-list does not publish. For the same reason there is no GET. One re-issue per update request: it restores access to the proof, it does not extend the request indefinitely. Lost a second time: send a new update request once the current one lapses, since a pending request with a live token is what holds the 7-day cooldown on that email and listing. A request whose token has already expired holds nothing, so its replacement can go out immediately. Rate limited per IP more tightly than the general API budget.

post/services/{slug}/reissue-token

Request

Base URL: https://x402-list.com/api/v1
URL: https://x402-list.com/api/v1/services/{slug}/reissue-token
Auth: none declared

Path parameters

slugstring required

Request body

request_idstring uuid required

emailstring email required

The email used to create the update request

Response

Accepted. The same body is returned whether or not a matching request exists

Example response

{
  "provenance": {
    "attribution": "Data: x402-list.com (CC BY 4.0)",
    "cite_as": "https://x402-list.com/services/acme-generate",
    "source": "https://x402-list.com"
  }
}

Changes

No recorded changes to this operation across all 1 revision of this API.