Developers — TAP
TAP Sessions
Work with session identifiers safely and simply. The TAP endpoints provide session lookup and high-level verification without exposing protocol internals.
Session Lookup
Look up a TAP session by its session identifier. Returns the session record if found, or a 404 response if the session does not exist in the ledger.
// Look up a session by ID
GET /api/racing-os-pro/tap/session/:sessionId
// Authorization required
Authorization: Bearer <token>
Returns the full session record if the session exists.
Returns 404 if the session identifier is not found.
Session identifiers are case-insensitive.
Session Verification
Verify a session identifier at a high level. The verification endpoint supports two modes: a ledger existence check (when only a session ID is supplied) and a full field verification (when all required fields are supplied).
// Verify a session
POST /api/racing-os-pro/tap/verify
// Mode B — ledger existence check (sessionId only)
{ "sessionId": "0x..." }
// Mode A — full field verification
{ "sessionId": "0x...", "wallet": "0x...", ... }
Mode B checks whether the session ID exists in the ledger. Suitable for sessions sourced from on-chain events where the wallet address is not available.
Mode A performs a full field verification. All required fields must be supplied.
Protocol internals — including hashing logic and ledger mechanics — are not exposed.