Skip to main content
Version: 1.8.1

Blockchain API - Token City

REST API for queries and transaction generation on the blockchain networks where Token City operates.

This is v1.8.1 — the current stable version. v2.0.0 is the next major version and introduces breaking changes.

Breaking changes in v2.0.0​

1. URL versioning prefix​

All v2.0.0 endpoints are served under a /v2/ path prefix (e.g. GET /v2/tokens/{tokenId}/holders). v1.8.1 has no prefix. If you only update the base URL you must also prepend /v2/ to every path.

2. Paginated list response shape​

In v1.8.1 list endpoints return a bare JSON array [ ... ]. In v2.0.0 every list endpoint returns a paginated envelope:

{ "items": [ ... ], "hasNext": true, "nextCursor": "..." }

Consumers that destructure or iterate the response directly will break.

Authentication​

All endpoints require HMAC authentication via three request headers:

  • Authorization: your API key
  • Date: UTC request timestamp in RFC 7231 format (e.g. Fri, 02 Feb 1996 03:04:05 GMT)
  • Signature: TC sha256 <hex-encoded-HMAC-SHA256-signature>

Error format​

All error responses use a consistent JSON envelope:

{ "success": false, "status": 400, "result": { "error": { "message": "..." } }, "requestId": "uuid" }

The requestId field is also returned as the X-Request-Id response header for correlation and support purposes.

Authentication​

Token City HMAC authentication. Authorization header = API key. Date header = UTC timestamp (RFC 7231). Signature header = TC sha256 <hex-encoded-HMAC-SHA256>.

Security Scheme Type:

apiKey

Header parameter name:

Authorization

Contact

Token City Support: [email protected]

URL: https://token-city.com