TimestampIt! API

Please refer to the example API clients repo for example implementations of Trusted Timestamp creation and verification.

Verification key endpoints

Endpoints for retrieving verification keys are non-authenticated. This allows for anyone to verify a trusted timestamp without needing to create a user account. There are two primary endpoints, one for retrieving verification keys individually, and one for retrieving all verification keys at once (the entire "keychain").

GET https://timestampit.com/key/<key id>

Retrieve a verification key. Authentication is not required. Users can request the key in various formats depending on their needs. See get verification key for more details including descriptions of the various formats the keys are available in.

GET https://timestampit.com/keychain

Return the entire keychain, from the genesis key to current signing key. This endpoint always returns JSON, regardless of any values set for the Accept header.

Authentication is not required for this endpoint.

Authentication

Authenticated endpoints on the TimestampIt! API use HTTP Basic Authentication.

In order to call an authenticated endpoint use the following steps:
- Create an account. You will need your username and password that you set when creating your account to make an authenticated API call.
- Set the Authorization request header to the correct HTTP Basic Authentication value and make your request.
- Most HTTP clients provide a built-in feature for HTTP Basic Authentication. However it is straightforward to construct the header manually. Set the Authorization header in accordance with this pseudo code: Authorization: Basic <Base64.encode("username:password")>.

Creating Trusted Timestamps

POST https://timestampit.com/create

This authenticated endpoint is used to create Trusted Timestamps. See create Trusted Timestamp for more details.

Other endpoints

GET /tt/<id>/as_file

This authenticated endpoint allows retrieval of existing Trusted Timestamps. Only Trusted Timestamps created by your account can be retrieved.

Users can set the Accept: application/json header to receive json. Otherwise it will be returned in simple format.