Traceport API

Create cryptographic proof that your records exist—without exposing the underlying data. When verification is needed, you provide the original. Anyone can confirm it's unchanged.

What the API does

Traceport creates blockchain-anchored proof records for your application data:

  1. Your app hashes data locally (SHA256)
  2. Submit hash to Traceport via simple API call
  3. Get back verification reference (blockchain transaction ID + certificate)
  4. Prove authenticity when needed—for audits, disputes, or compliance

What goes on blockchain: Only the cryptographic hash (immutable proof)
What stays in your control: Original data, user workflows, application logic

How verification works

Every attestation includes multiple layers of cryptographic proof. Some are publicly verifiable anytime. Others require you to provide the original data—giving you control over when and with whom you share it.

Always Public

✓ Blockchain Existence

Proof the record was created at a specific moment in time

Always Public

✓ Digital Signature

Cryptographic proof of authenticity

Always Public

✓ Organization Identity

Which organization issued this attestation

On Demand

✓ Data Integrity

You provide the data, verifier confirms it matches the hash

The notary model: Like a traditional notary, Traceport stamps your record without keeping a copy. The stamp is public proof. When someone needs to verify the contents, you show them the original—they can mathematically confirm it hasn't changed.

Real application example

Traceport for Charities is a complete donation platform built on this API—demonstrating one integration pattern where the application chooses to make data publicly verifiable:

  • Donors give through Next.js web application
  • App stores donation data in Supabase (their own database)
  • App hashes donation data client-side
  • App sends hash to Traceport API
  • Traceport returns blockchain proof + verification URL
  • Donor receives QR code certificate
  • App provides a public endpoint for data verification (because transparency is the goal)

Your choice: The charity app makes donation data publicly verifiable because donor transparency is the point. For enterprise use cases—contracts, audits, compliance—you may prefer to keep data private and verify only when needed. Both patterns work with the same API.

What you get

  • Organizational Identity: Cryptographically isolated keyspace per organization
  • Custom Protocols: Define your own attestation types (donations, contracts, certifications, etc.)
  • Multi-Layer Verification: Public blockchain proof + on-demand data verification
  • QR Code Certificates: Professional verification documents for each attestation
  • Standards Compliant: Built on BRC-42, BRC-43, and BRC-74 BSV blockchain standards
  • Forever Verifiable: Proofs work independently—verification remains possible even if Traceport disappears

Industry examples

  • Legal: Contract signatures, legal filings, notarization, IP timestamps
  • Healthcare: Medical credentials, clinical trials, HIPAA compliance, prescription verification
  • Supply Chain: Shipment tracking, chain of custody, quality inspections, origin verification
  • Finance: Audit trails, regulatory filings, transaction records, compliance documentation
  • Education: Academic transcripts, certifications, course completions, credential verification
  • Government: Permits, licenses, inspections, public records, safety compliance

API request format

Submit attestations with a simple POST request:

Endpoint

POST https://api.traceport.io/api/v1/attest

Request

curl -X POST https://api.traceport.io/api/v1/attest \
  -H "Authorization: Bearer YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "payload": "f7a3b8c9d2e1a4b7c6d8e9f0a1b2c3d4...",
    "protocol": "contracts"
  }'

Response

{
  "success": true,
  "txid": "9b9c2781e1ed15f200bc42d01803e89e...",
  "verification": {
    "url": "https://api.traceport.io/verify/9b9c2781...",
    "txid": "9b9c2781e1ed15f200bc42d01803e89e..."
  },
  "usage": {
    "quota": 1000,
    "used": 247,
    "remaining": 753
  }
}

The payload is a SHA256 hash of your data (hex encoded). The protocol is your custom attestation type.

Verification endpoint

Every attestation gets a verification URL. When someone visits it, they see:

  • Public proof: Blockchain existence, digital signature, and organization identity—verified in real-time
  • Data verification: Instructions for how to verify the original data matches the hash (requires you to provide the data)
  • Blockchain link: Direct link to view the transaction on a public block explorer

For applications that want full public verification (like the charity app), you can build an endpoint that serves the original data—the verification page will automatically use it.

Technical foundation

Traceport implements the Bitcoin SV (BSV) blockchain standards for cryptographic attestations. These standards ensure long-term interoperability and independent verification capabilities—your proofs remain verifiable regardless of any single company's continued operation.

Get started

Start building with the same API that powers Traceport for Charities. Request a sandbox API key for 100 free attestations.

Request API Key Request Documentation Access