• Language

  • Non-English translations are machine-generated.

  • Language Preferences
  • Theme
Sign In

Knowledge Base

Browse the concepts behind Truestamp. Follow the links between concepts, or search across everything.

Tagged: json-api

7
Accounts
API Keys for Programmatic Access Long-lived Truestamp API keys presented as Authorization Bearer credentials to authenticate the JSON:API, GraphQL, and console surfaces, how a key is created, revoked, and audited, and how they differ from OAuth 2.1 used by the MCP surface.
API
Beacon API The authenticated programmatic beacon surfaces - JSON:API endpoints under /api/json/beacons (list, latest, by id, by hash), the equivalent GraphQL queries, the four-field beacon object, error and rate-limit behavior including the rate_limited code, and beacon proof generation by block id. JSON:API HTTP Surface The authenticated JSON:API REST surface at /api/json, its API-key or OAuth bearer auth, the OpenAPI spec plus Swagger UI and ReDoc discovery pages, resource-oriented endpoints, tenant selection, filtering, and pagination conventions. Outgoing Webhooks Register and manage HTTPS webhook endpoints over the authenticated JSON:API, GraphQL, and MCP surfaces to receive item event callbacks, with optional bearer-token auth, delivery tracking, and private-IP SSRF safeguards. Utility Endpoints The seven stateless utility endpoints under /api/json/utilities (hash, verify-hash, uuidv7-timestamp, ulid-timestamp, resolve-id, jcs-canonicalize, server-time) and their GraphQL query twins, with request and response shapes, the result envelope, auth and OAuth scopes, and resolve-id gating.
Glossary
JSON:API Truestamp's authenticated REST surface at /api/json following the JSON:API specification, with API-key or OAuth 2.1 bearer authentication, an OpenAPI spec rendered by Swagger UI and ReDoc, and resource endpoints with standard filtering, sorting, and pagination.
Items
Submit an Item How to timestamp data by submitting an item on the web form, JSON:API, GraphQL, console WebSocket, CLI, or an MCP agent, with every claims field (name, hash and hash type, description, URL, location, timestamp, metadata), hash mode versus plan-gated claims-only mode, and the limits that apply.