https://api.tzstamp.io
You can run your own aggregator server and use our management utility to deploy your own contract to any Tezos network.
POST /stamp
Submits a hash to be aggregated.
The Content-Type
header must be one of application/json
or
application/x-www-form-urlencoded
.
The payload must have a data
field containing a hexadecimal representation of a SHA-256 hash.
{ "data": "01234..." }
data=01234...
The server will respond with a URL at which the proof will be published and seconds until next
publication, not including time to on-chain inclusion and confirmation. The response will be plain
text by default, but a JSON object can be requested with an Accept
header with value
application/json
:
{
"url": "https://api.tzstamp.io/proof/01234...",
"secondsToPublication": "1000"
}
$ curl https://api.tzstamp.io/stamp -d data=40cb6ac0645f648a12d0aab7df480796fc4165609a65ea430018d9b3af68b76d
GET /proof/:id
Retrieves a proof by ID from the server.
The server will respond with the one of the following:
200 OK
— The proof is included in the body, encoded in JSON.
202 Accepted
— The timestamp proof is pending publication and confirmation.
404 Not Found
— The proof either does not exist or has been deleted from the server
cache.
$ curl https://api.tzstamp.io/proof/80eb84095823ec33a1d00dadf844028082f384b760f189b7ccc442f7b5b63969 -o myfile.proof.json
GET /status
Fetches the current status of the server. Includes the following information:
The response will be plain
text by default, but a JSON object can be requested with an Accept
header with value
application/json
:
{
"proofVersion": 1,
"network": "NetXdQprcVkpaWU",
"contract": "KT1AtaeG5PhuFyyivbfPZRUBkVMiqyxpo2cH",
"secondsToPublication": "1000"
}