Skip to main content
GET
Check server time
Use this endpoint to measure the offset between your host’s clock and the Bloobank server clock. The signed X-Access-Timestamp header must stay within ±10 seconds of server time, so checking the offset before your first authenticated call — and periodically thereafter — prevents intermittent TIMESTAMP_SKEW_EXCEEDED rejections. This endpoint requires no authentication: no signing headers, no credentials. That also makes it a convenient connectivity check before onboarding is complete.
  1. Call GET /time and read your local clock immediately around the call.
  2. Compute offset = epochMs − localTimeMs (optionally correct for half the round-trip).
  3. Apply the offset when signing: X-Access-Timestamp = Date.now() + offset.
  4. Re-check periodically — and on any TIMESTAMP_SKEW_EXCEEDED error — since clocks drift.
The epochMs field uses the exact same representation as X-Access-Timestamp (Unix epoch milliseconds, UTC), so it compares directly against Date.now() and equivalents. For the platform’s time model, see Date & time. If your requests are rejected with clock-related errors, see Troubleshooting.

Authorizations

X-Access-Signature
string
header
required

Response

The current server time.

Snapshot of the server's current time, used to measure clock skew before signing requests.

time
string<date-time>
required

Current server time as an ISO 8601 UTC string with millisecond precision.

Example:

"2026-08-05T12:00:00.000Z"

epochMs
integer<int64>
required

Current server time in milliseconds since the Unix epoch — the same format expected in the X-Access-Timestamp header.

Example:

1754392800000