🥔TSA Methods
Methods used to obtain Qualified Electronic Timestamps for documents
Qualified Electronic Time stamping of document hashes according to RFC3161
Access to the service can be secured in two ways. either using API-KEY or using HTTP Basic Authentication
post
Path parameters
processIdinteger · int32Required
Header parameters
API-KEYstringOptional
Responses
200
Success
post
POST /tsa/stamp/rfc3161/{processId} HTTP/1.1
Host:
Accept: */*
200
Success
No content
The hash to sign needs to be send in the request body as application/octet-stream
Stamp the document hash
post
Path parameters
processIdinteger · int32Required
Header parameters
API-KEYstringOptional
Body
hashstring | nullableOptional
Responses
200
Success
post
POST /tsa/stamp/{processId} HTTP/1.1
Host:
Content-Type: application/json
Accept: */*
Content-Length: 15
{
"hash": "text"
}200
Success
No content
The document hash to be processed needs to be send in the request as JSON. The value of the hash field must be encoded according to BASE64.
For this method, access is secured only using API-KEY
Last updated