Documentation

API Documentation/v1

Verify Data (Using Source Data)

Verify data by sending the source file and optionally a proof file. Returns verification results with blockchain validation details.

AttributeDetails
MethodPOST
DescriptionThis endpoint is used to submit one or two files for data verification against the blockchain. It processes the provided data and proof (if provided) and returns the verification results.
Endpointhttps://integritas.technology/core/v1/verify/post

NFT Proof Trace (Optional Feature)

The NFT Proof Trace is an optional feature in the API that allows you to request an NFT trace of the verification process.

When enabled:

  • It provides an immutable, on-chain record of the validation.
  • The verification is linked to a unique NFT, ensuring transparency and traceability.

Request Headers

HeaderValueDescription
Content-Typemultipart/form-dataSpecifies the content type as multipart form data
x-api-keyyour-api-keyAdd your API-key from your profile at https://integritas.technology/
x-report-requiredtrue / falseRequest NFT trace from the verification process
x-request-idyour-choiceAdd a request id to trace every step of the process

Request Body (Choose one)

Request TypeContent-TypeBody TypeKeysDescription
File uploadmultipart/form-dataform-datafileValidate a source file.
File uploadmultipart/form-dataform-datafileValidate a .tar file. The .tar file should contain the source file and a JSON proof file.
File uploadmultipart/form-dataform-datafile, jsonproofValidate a source file with a JSON proof file.

Note: Uploading Hash to Blockchain

When verifying with only a source file (without a proof file), the file's hash must already exist on the blockchain to receive a match result.

To upload a hash to the blockchain, you can send it directly from your own Minima node using this terminal command:

send address:0x29f774d99ae3e3494ee4a69f3a11a8248362506a9b9bc526f8c98ab6deca68f5 amount:0.000000000000001 state:{"99":"[YOUR_HASH]"}

Replace [YOUR_HASH] with your actual file hash. This sends the transaction from your own node directly to the blockchain.

Request Examples

curl -X POST https://integritas.technology/core/v1/verify/post \
  -H "x-api-key: your-api-key" \
  -H "x-request-id: your-choice" \
  -H "x-report-required: true" \
  -F "file=@path/to/yourfile.pdf" \
  -F "jsonproof=@path/to/yourproof.json"

API Demo

Try the endpoint with your own API key, source file, and optional proof file. The request is sent directly to the API, and the response is displayed below.

Your API key is only used for this request and is not stored.

Get your API key from integritas.technology

Add a request ID to trace every step of the process

Upload the JSON proof file if you have one

API Response

The response from the API contains information about a file and its results from on-chain verification.

Example Response (No Match)

{
  "service": "CORE_API",
  "apiVersion": 1,
  "requestId": "verify-data-no-match",
  "status": "success",
  "statusCode": 200,
  "message": "Verification complete",
  "timestamp": "2026-01-16T14:46:32.657Z",
  "data": {
    "service": "SEARCH_API",
    "api_version": 1,
    "requestId": "verify-data",
    "response_time": "56118.07 ms",
    "response": {
      "fileHash": "0xE630FCDE204036E93323AE99843BF0EC6D03CAEB51CBBEA11E03D6739F8E9C3F",
      "fileName": "source_256kb.pdf",
      "fileSize": 262144,
      "result": "no match",
      "nftcoinid": "0xDC080F44E554B85E5663D1F1BED2F83DB8F3BCD995ED22713198238096C713A3",
      "nfttxnid": "0x000009C453D5CD4E70A45099BD8958F8427E60B8DA3D9C10F2BDB754430ABA6E",
      "method": "all tested",
      "hash_instances_onchain": 0,
      "unique_hashes": 0,
      "blockchain_data": [],
      "fileSegments": []
    }
  }
}

Example Response (Full Match)

{
  "service": "CORE_API",
  "apiVersion": 1,
  "requestId": "verify-data-full-match",
  "status": "success",
  "statusCode": 200,
  "message": "Verification complete",
  "timestamp": "2026-01-16T14:48:45.654Z",
  "data": {
    "service": "SEARCH_API",
    "api_version": 1,
    "requestId": "verify-data",
    "response_time": "8643.46 ms",
    "response": {
      "fileHash": "0xE630FCDE204036E93323AE99843BF0EC6D03CAEB51CBBEA11E03D6739F8E9C3F",
      "fileName": "source_256kb.pdf",
      "fileSize": 262144,
      "result": "full match",
      "nftcoinid": "0xE037730318B921420FB757EFCD56544DF7AB4C49A078015221446950C0C57CD5",
      "nfttxnid": "0x000011F540D77A200E692D458421D434CF1D846D8E3491C897E99E08CC931377",
      "method": "timestamp",
      "hash_instances_onchain": 1,
      "unique_hashes": 1,
      "blockchain_data": [
        {
          "block_number": 1898484,
          "block_date": "2026-01-16 14:26:12",
          "txpow_id": "0x000000389FDEEAF4537124C1BE40A352065A7E945FDCF3261EBF328828934D81",
          "transactionid": "0x00002738DD716B9B89FECDDE97677CDC628B40542930269D18FEEEF245CBC689",
          "coin_id": "0x907671CF2F571DAAB8C720E1C89711E0568AE13638CAF307BDB7371D1DBAA5DD",
          "matched_hash": "0xE630FCDE204036E93323AE99843BF0EC6D03CAEB51CBBEA11E03D6739F8E9C3F"
        }
      ],
      "fileSegments": [
        {
          "matched_hash": "0xE630FCDE204036E93323AE99843BF0EC6D03CAEB51CBBEA11E03D6739F8E9C3F",
          "offset": 0,
          "packetSize": 262144
        }
      ]
    }
  }
}

Response Fields

For a complete description of the shared verification response schema used by this endpoint, including blockchain_data and fileSegments, see API Response Schema — Verification Response.

Get Proof

Retrieve proof of stamped data by sending the UID from the previous response. This is the third step in the stamping process.

Verify Hashed Data (Using Only Proof File)

Verify data using only a proof file. This endpoint requires NFT trace and returns verification results with blockchain validation details.

On this page