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.

Attribute	Details
Method	`POST`
Description	This endpoint is used to submit one proof file for data verification against the blockchain. It processes the proof (if provided) and returns the verification results.
Endpoint	`https://integritas.technology/core/v1/verify/post-lite`

Request Headers

Header	Value	Description
Content-Type	`application/json`	Specifies the content type as JSON
x-api-key	`your-api-key`	Add your API-key from your profile at https://integritas.technology/
x-report-required	`true`	Request NFT trace from the verification process
x-request-id	`your-choice`	Add a request id to trace every step of the process

Request Body

Request Type	Content-Type	Body Type	Keys	Description
File upload	`file`	`form-data`	`jsonproof`	Validate a JSON proof file.

Request Examples

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

API Demo

Try the endpoint with your own API key and 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.

API Response

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

Example Response (Full Match)

{
  "service": "CORE_API",
  "apiVersion": 1,
  "requestId": "verify-hash-full-match",
  "status": "success",
  "statusCode": 200,
  "message": "Verification complete",
  "timestamp": "2026-01-16T14:52:10.655Z",
  "data": {
    "service": "SEARCH_API",
    "api_version": 1,
    "requestId": "verify-hash",
    "response_time": "6180.00 ms",
    "response": {
      "fileHash": "0xE630FCDE204036E93323AE99843BF0EC6D03CAEB51CBBEA11E03D6739F8E9C3F",
      "nftcoinid": "0xC55AF5704F1F47306A3964DB34366C7415D1590B1B948B40B1340FFD10E8EFD5",
      "nfttxnid": "0x000016208F633E7BB875B494A36B15CCCD518715B43C487FB1E5A5CD9FC7C780",
      "data": {
        "result": "full match",
        "validationMethod": "timestamplite",
        "blockchain_data": [
          {
            "block_number": 1898484,
            "block_date": "2026-01-16 14:26:12",
            "txpow_id": "0x000000389FDEEAF4537124C1BE40A352065A7E945FDCF3261EBF328828934D81",
            "transactionid": "0x00002738DD716B9B89FECDDE97677CDC628B40542930269D18FEEEF245CBC689",
            "coin_id": "0x907671CF2F571DAAB8C720E1C89711E0568AE13638CAF307BDB7371D1DBAA5DD",
            "matched_hash": "0xE630FCDE204036E93323AE99843BF0EC6D03CAEB51CBBEA11E03D6739F8E9C3F"
          }
        ]
      }
    }
  }
}

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.