Overview (v1)

This documentation provides a detailed overview of the Integritas API, which enables both uploading and verification of data hashes against the blockchain. It supports optional NFT traceability and returns structured results that include on-chain validation details. Use this guide to understand endpoints, request formats, and how to interpret the verification responses.

Base URL

All API requests are made to the following base URL:

https://integritas.technology/core

Example

To make a request to the "Get file hash" endpoint, you would use:

https://integritas.technology/core/v1/file/hash

Authentication

Authentication is required and done through the use of API-keys. Get yours at https://integritas.technology/.

Endpoints Overview

There are five available endpoints.

Stamping Data

Three endpoints are used for stamping data:

Send file and get hash - Prepare data to be stamped by hashing it. You will receive the SHA3-256 hash of the data in the response.
Send hash and get UID - Stamp data by uploading the hashed data. You will receive a UID in the response.
Get proof - Retrieve proof of stamped data by sending the UID from the previous response.

Verification

Two endpoints are used for verifying data:

Verify data (Using source data) - Verify data by sending the source file and optionally a proof file.
Verify hashed data (Using only proof file) - Verify data using only a proof file.

Quick Reference

Endpoint	Method	Path	When to Use
Get file hash	`POST`	`/v1/file/hash`	Generate the SHA3-256 hash for raw source data prior to stamping.
Get UID	`POST`	`/v1/timestamp/post`	Submit an already computed hash to receive a UID that represents the stamp.
Get proof	`POST`	`/v1/timestamp/status`	Retrieve on-chain proof for one or more UIDs after stamping.
Verify with file	`POST`	`/v1/verify/post`	Validate a source file (and optional proof) directly against the blockchain.
Verify with proof	`POST`	`/v1/verify/post-lite`	Validate by sending only the JSON proof file; NFT trace header required.

For details on the response envelopes and field structures used by these endpoints, see the API Response Schema.