TimeBinder

Start →

For developers

TimeBinder Developer API Timestamp SHA-256 file hashes on Bitcoin from your own systems

Timestamp file hashes on the Bitcoin blockchain from your own systems, and read your TimeBinds back. Your files never leave your servers.

Sign up to the API → Read the API docs

What is the TimeBinder API?

Short answer: the TimeBinder® API is a JSON REST API that lets your own software submit SHA-256 file hashes to be timestamped on the Bitcoin blockchain, then fetch the resulting TimeBinds. You hash files on your own servers and send only the hashes, so the files themselves are never sent to TimeBinder. TimeBinds created through the API are charged to your Token balance at the same rates as the app, and they appear in your TimeBinder dashboard alongside the ones you make there. The full technical reference is at api.timebinder.io.

What is TimeBinder? TimeBinder is a blockchain timestamping service. It shows that a digital file existed no later than a specific time, and that it still matches its fingerprint, by anchoring the file’s SHA-256 fingerprint to the Bitcoin blockchain. Files are hashed in your browser and never uploaded, and each TimeBind comes with a Proof of Time Certificate that can be checked later. It does not prove who created a file or that its contents are true.

What you can do with the API

A short overview. The API reference has the endpoints, fields and examples.

  • Submit a TimeBind. Send up to 10 file hashes in one request and choose Pooled or ASAP. You can add your own reference and details, which are hashed into the TimeBind.
  • List and fetch TimeBinds. Read the status, Bitcoin transaction ID and details of every TimeBind on your account, including ones created in the app.
  • Get callbacks. Have TimeBinder notify your server when a TimeBind is submitted and when it is confirmed on the Bitcoin blockchain. Callbacks are signed so you can check they came from us.
  • Check your Token balance. See how many Tokens you have left before you submit.
  • Verify files yourself. Each TimeBind comes back with the proof data your system needs to check a file against the Bitcoin transaction.
  • Control access with API keys. Each key has its own permissions (view, submit Pooled, submit ASAP) and an optional expiry date.

What teams use the TimeBinder API for

  • Document management and practice systems. TimeBind a final PDF the moment it is approved or signed, and store the TimeBind ID with the record.
  • Evidence and inspection apps. Hash photos and reports on the device or server at capture, then submit the hashes in batches of up to 10.
  • Build and release pipelines. TimeBind release artefacts, source archives or SBOMs at each tagged release. See source code timestamping.
  • Research and data pipelines. TimeBind dataset snapshots or notebook exports before analysis or submission.
  • Creative platforms. Let your users date their uploads without you holding a second copy of their files.

In each case only the SHA-256 hash leaves your systems. A TimeBind shows the file existed no later than the recorded time and still matches its fingerprint. It doesn’t show who created it.

How it works

  1. Sign in to the TimeBinder app and create an API key, choosing what it is allowed to do.
  2. Hash your files with SHA-256 on your own servers. The files stay with you.
  3. Send the hashes to the API as a Pooled or ASAP TimeBind. The Tokens are taken from your balance.
  4. Wait for the callback, or check the TimeBind, until it is confirmed on the Bitcoin blockchain.
  5. Keep the proof data with your records so the file can be checked later.

If API access isn’t switched on for your account yet, send us a request below and we’ll help you get set up.

Good to know

  • Keep API keys secret. Call the API from your servers only, never from a browser or mobile app.
  • Plans with API access. API access is included in the Business, Business Plus and Enterprise plans. Business is USD $149 a month for 60 Tokens, Business Plus is USD $299 a month for 150 Tokens, and Enterprise is custom. API TimeBinds use Tokens from your balance at the same rates as the app. See TimeBinder pricing and business plans.
  • Limits. Limits on API use are covered in the Terms and Conditions.
  • Questions, including testing. For API questions, including testing, get in touch via the Contact page.
  • Pooled or ASAP. Pooled TimeBinds are grouped with others and usually recorded within 24 to 48 hours, and often sooner, depending on Bitcoin network activity. ASAP TimeBinds get their own Bitcoin transaction, broadcast straight away, but that does not mean instant confirmation. Compare Pooled and ASAP.
  • What a TimeBind shows. That a file existed no later than the time recorded on the Bitcoin blockchain, and that it still matches its fingerprint. It does not show who created the file or that its contents are true.

Working out Token usage

Each Pooled TimeBind uses 1 Token and each ASAP TimeBind uses 3 Tokens, whether created in the app or through the API. One TimeBind can cover up to 10 file hashes. For example, 100 Pooled TimeBinds a month use 100 Tokens; 30 ASAP TimeBinds use 90 Tokens. For regular volume, see Business plans and which plan do I need.

Sign up to the API

Tell us a little about what you want to build. A person on our team will reply by email to help you get API access.

We only use these details to reply to your request about API access. See our privacy policy.

Developer API FAQ

Are my files uploaded when I use the API?

No. You work out each file’s SHA-256 hash on your own systems and send only the hash. The files themselves never leave your servers.

Which plans include API access?

API access is included in the Business, Business Plus and Enterprise plans. TimeBinds created through the API use Tokens from your balance at the same rates as the app. See TimeBinder pricing.

Are there limits on API use?

Yes. Limits on API use are covered in the Terms and Conditions.

Who do I ask about testing the API?

For API questions, including testing, get in touch via the Contact page.

Do I need to send the file to verify it later?

No. Re-hash the file on your side and compare it with the hash in the TimeBind. ASAP TimeBinds can be checked independently against the Bitcoin transaction; Pooled TimeBinds are verified through TimeBinder.

Can I choose Pooled or ASAP through the API?

Yes. Each request can ask for a Pooled or an ASAP TimeBind, as long as your API key has permission for that type.

Can other people verify a TimeBind made through the API?

Pooled TimeBinds are verified through TimeBinder; ASAP TimeBinds can be verified independently from the certificate and the Bitcoin blockchain. Checking a TimeBind is always free.

Where is the full API documentation?

The technical reference, with endpoints, request fields, errors, callbacks and examples, is at api.timebinder.io.

How do I get access?

Sign in to the TimeBinder app to create an API key. If API access isn’t enabled on your account yet, or you have questions first, use the form on this page and we’ll reply by email.

Related pages