← Boss Tag

Developer Docs

Boss Tag Record API · v1

Build on the record layer

The Boss Tag API lets you issue records and read the public record layer — the certificate, the on-chain anchor, and the public /verify page. Boss Tag surfaces each issuer’s own authentication as the issuer’s; it is not itself an authentication service.

Quick start

# Install the Boss Tag SDK (optional)

npm install @bosstag/sdk

# Or use the REST API directly

curl -X GET \

https://www.bosstag.co/api/assets \

-H "Authorization: Bearer YOUR_API_KEY"

View authentication guide →

Base URL

https://www.bosstag.co/api

Format

JSON

Auth

Bearer token

Version

v1

On-chain records · Polygon mainnet

Each issued record is anchored as a keccak256 record-integrity commitment — a hash, not a token. The commitment is written to the BossTagAnchor registry and is independently checkable on Polygonscan.

BossTagAnchor · record registry

0xbB30Dacab1EebE152A4517F617cDCF51DB5DEbc3

The contract every /verify record anchors to. Stores keccak256(recordHash) → sequence. This is the canonical anchor.

BossTagAsset · asset contract

0x0337E177a58e547D08E76Acd001B72a704EA0bf2

A separate contract — NOT the record anchor. Don't treat this address as the on-chain record.

Recompute the record hash (v1)

# canonical string, "|"-joined, then keccak256 of its UTF-8 bytes

canonical = "bosstag-cert-v1" | assetId | title | certNumber | issuedAt

recordHash = keccak256(utf8Bytes(canonical))

  • assetId — the record's UUID (the /verify identifier).
  • title — the item's display name.
  • certNumber — the certificate number shown on the record.
  • issuedAt — the issue date, ISO YYYY-MM-DD.
  • The version prefix bosstag-cert-v1 is part of the hash — a canonicalization change bumps the version.

Need help integrating?

contact@bosstag.co