### GET /v1/time/current

Source: https://timelogicapi.com/docs

Retrieves the current time for a specified timezone. This is the first request example shown in the getting started guide.

```APIDOC
## GET /v1/time/current

### Description
Retrieves the current time for a specified timezone.

### Method
GET

### Endpoint
https://api.timelogicapi.com/v1/time/current

### Parameters
#### Query Parameters
- **tz** (string) - Required - Timezone identifier, e.g., Europe/Paris.

### Request Example
curl "https://api.timelogicapi.com/v1/time/current?tz=Europe/Paris" \
  -H "Authorization: Bearer $TIMELOGIC_API_KEY"

### Authentication
Authorization: Bearer YOUR_TIMELOGIC_API_KEY

Alternatively, use X-API-Key header or api_key query parameter.

```

--------------------------------

### GET /v1/time/diff

Source: https://timelogicapi.com/docs

Calculates the duration between two specifier-encoded instants. Supports business days and holiday adjustments.

```APIDOC
## GET /v1/time/diff

### Description
Calculates the duration between two specifier-encoded instants. Supports business days and holiday adjustments.

### Method
GET

### Endpoint
https://api.timelogicapi.com/v1/time/diff

### Parameters
#### Query Parameters
- **from** (string) - Required - Embedded specifier for the start instant. Examples: `unix=1711300000`, `iso=2026-04-16T09:00:00`, `now`.
- **to** (string) - Required - Embedded specifier for the end instant. Examples: `iso=2026-04-30T00:00:00Z`.
- **business_days** (boolean) - Optional - When `true`, includes a `business_days` count in the response.
- **holiday_country** (string) - Optional - ISO 3166-1 alpha-2 country code to subtract public holidays.
- **holiday_subdivision** (string) - Optional - Regional calendar code (e.g., `ENG`, `CA`) for regional holidays.

### Request Example
curl "https://api.timelogicapi.com/v1/time/diff?from=iso=2026-01-02T00:00:00Z&to=iso=2026-04-30T00:00:00Z&business_days=true&holiday_country=FR" \
  -H "Authorization: Bearer $TIMELOGIC_API_KEY"

### Response
#### Success Response (200)
- **business_days** (integer) - Number of business days between the two instants, when `business_days=true`.

#### Error Response (400)
- **error** (string) - Error code `INVALID_PARAMETER` with message "Unsupported holiday calendar" when the holiday country is not supported.
```

--------------------------------

### GET /.well-known/time-api-public-key

Source: https://timelogicapi.com/docs

Fetches the public keys used to verify signed responses. Cache keys by kid; historical keys may remain available after rotation.

```APIDOC
## GET /.well-known/time-api-public-key

### Description
Fetches the public keys used to verify signed responses. Cache keys by kid; historical keys may remain available after rotation.

### Method
GET

### Endpoint
https://api.timelogicapi.com/.well-known/time-api-public-key

### Response
#### Success Response (200)
- **keys** (array) - List of public JWK keys, each with a `kid`.

#### Response Example
{
  "keys": [
    {
      "kid": "example-key-id",
      "kty": "RSA",
      "use": "sig",
      "alg": "RS256",
      "n": "...",
      "e": "AQAB"
    }
  ]
}
```

--------------------------------

### GET /v1/time/clock

Source: https://timelogicapi.com/docs

Returns a self-bootstrapping HTML fragment for an embeddable clock. The style parameter is required and must be one of 30 named styles. Responses are uncached.

```APIDOC
## GET /v1/time/clock

### Description
Returns a self-bootstrapping HTML fragment: a host <div>, a JSON config <script>, and <link>/<script> tags pointing at the hosted CSS and JS bundle. Drop the entire snippet anywhere on your page.

### Method
GET

### Endpoint
/v1/time/clock

### Parameters
#### Query Parameters
- **tz** (string) - Optional - Timezone identifier, e.g. Europe/Paris.
- **style** (string) - Required - Must be one of 30 named styles (10 analog + 20 digital).

### Request Example
curl "https://api.timelogicapi.com/v1/time/clock?tz=Europe/Paris&style=analog-station" \
  -H "Authorization: Bearer $TIMELOGIC_API_KEY"

### Response
#### Success Response (200)
Returns an HTML fragment containing the clock markup and assets.

### Error Handling
Errors are JSON with a stable shape. Common codes include INVALID_PARAMETER for bad style values.
```

--------------------------------

### Standard error response JSON

Source: https://timelogicapi.com/docs

Example of the stable JSON error shape returned by the API. It includes an error object with a code, message, and details, plus a request_id. Common codes include INVALID_PARAMETER, INVALID_TIMESTAMP, MISSING_TARGET, AMBIGUOUS_TARGET, 429, and 5xx.

```json
{
  "error": {
    "code": "INVALID_PARAMETER",
    "message": "Invalid timezone.",
    "details": { "tz": "Not/AZone" }
  },
  "request_id": "3534e3fe-f916-4d44-a50b-8f92a74074c4"
}
```

--------------------------------

### Authenticate with api_key query parameter

Source: https://timelogicapi.com/docs

Use this method for constrained clients that cannot set custom headers. Note that query-string credentials may be logged or exposed in referrers.

```bash
curl "https://api.timelogicapi.com/v1/time/current?tz=Europe/Paris&api_key=$TIMELOGIC_API_KEY"
```

--------------------------------

### Make a first request with cURL

Source: https://timelogicapi.com/docs

Use this cURL command to fetch the current time for a specific timezone using your API key stored in the TIMELOGIC_API_KEY environment variable.

```bash
curl "https://api.timelogicapi.com/v1/time/current?tz=Europe/Paris" \
  -H "Authorization: Bearer $TIMELOGIC_API_KEY"
```

--------------------------------

### Calculate business days with /v1/time/diff

Source: https://timelogicapi.com/docs

Calculate the duration between two instants with business day filtering enabled for a specific country.

```bash
curl "https://api.timelogicapi.com/v1/time/diff?from=iso=2026-01-02T00:00:00Z&to=iso=2026-04-30T00:00:00Z&business_days=true&holiday_country=FR" \
  -H "Authorization: Bearer $TIMELOGIC_API_KEY"
```

--------------------------------

### Fetch an embeddable clock with curl

Source: https://timelogicapi.com/docs

Use this curl command to retrieve the embeddable clock HTML fragment from /v1/time/clock. The style parameter is required and must be one of 30 named styles (10 analog + 20 digital). Responses are uncached, so each fetch reflects the current request.

```bash
curl "https://api.timelogicapi.com/v1/time/clock?tz=Europe/Paris&style=analog-station" \
  -H "Authorization: Bearer $TIMELOGIC_API_KEY"
```

--------------------------------

### Signature input format for v1

Source: https://timelogicapi.com/docs

The structure of the X-TimeLogic-Signature-Input header, which must be decoded as Base64URL UTF-8.

```text
v1
kid:<key id>
status:<HTTP status>
method:<HTTP method>
path:<origin-form path and query>
timestamp:<Unix seconds>
content-sha256:<standard-base64 SHA-256>

```

--------------------------------

### Authenticate with X-API-Key header

Source: https://timelogicapi.com/docs

An alternative header-based authentication method for direct API requests.

```http
X-API-Key: YOUR_TIMELOGIC_API_KEY
```

--------------------------------

### Fetch public keys

Source: https://timelogicapi.com/docs

Retrieve the public keys from the well-known endpoint to verify signed responses.

```http
GET https://api.timelogicapi.com/.well-known/time-api-public-key
```

--------------------------------

### Bulk time conversion request

Source: https://timelogicapi.com/docs

Converts a single Unix timestamp into multiple target offsets using the offset selector.

```bash
# convert one instant into three target offsets
curl "https://api.timelogicapi.com/v1/time/convert?unix=1711300000&offset=-04:00,%2B00:00,%2B09:00" \
  -H "Authorization: Bearer $TIMELOGIC_API_KEY"
```

--------------------------------

### Bulk current time request

Source: https://timelogicapi.com/docs

Retrieves the current time for multiple time zones in a single request using the tz selector.

```bash
curl "https://api.timelogicapi.com/v1/time/current?tz=Europe/Paris,Asia/Tokyo,America/New_York" \
  -H "Authorization: Bearer $TIMELOGIC_API_KEY"
```

--------------------------------

### Authenticate with Authorization header

Source: https://timelogicapi.com/docs

The standard method for authenticating direct API requests using a Bearer token.

```http
Authorization: Bearer YOUR_TIMELOGIC_API_KEY
```

--------------------------------

### Signed Response Request

Source: https://timelogicapi.com/docs

Set sign=true on a supported JSON route to receive a cryptographically signed response. Supported routes are current, convert, diff, add, calendar, DST, elapsed, and timezone. The /v1/time/clock route does not support signing.

```APIDOC
## [GET] /v1/time/current?tz=Europe%2FLondon&sign=true

### Description
Request a signed response from a supported JSON route by setting sign=true. The response body is unchanged, but the gateway adds signature-related headers.

### Method
GET

### Endpoint
/v1/time/current?tz=Europe%2FLondon&sign=true

### Parameters
#### Query Parameters
- **tz** (string) - Required - Timezone identifier, URL-encoded.
- **sign** (boolean) - Required - Must be exactly true to request a signature.

### Response
#### Success Response (200)
- **X-TimeLogic-Key-Id** (string) - JWKS kid for the public key that verifies this response.
- **X-TimeLogic-Signature-Alg** (string) - Signature algorithm: Ed25519.
- **X-TimeLogic-Signature-Timestamp** (integer) - Unix seconds used in the envelope.
- **X-TimeLogic-Content-SHA256** (string) - Standard-base64 SHA-256 of the exact response body bytes.
- **X-TimeLogic-Signature-Input** (string) - Base64URL encoding of the exact UTF-8 v1 envelope that was signed.
- **X-TimeLogic-Signature** (string) - Standard-base64 Ed25519 signature over the decoded Signature-Input bytes.

#### Response Example
(No response body example provided in the source.)

### Notes
- sign=false, a bare ?sign, or repeated sign values do not request a signature.
- The envelope does not include scheme, host, or Content-Type.
- Decode X-TimeLogic-Signature-Input as Base64URL UTF-8 to get the v1 envelope.
- The envelope contains newline-separated fields: v1, kid, status, method, path, timestamp, content-sha256.
- The path includes the query string, including sign=true.
- Do not rebuild a signing input from the URL host or response content type; decode and verify the header exactly as received.
```

=== COMPLETE CONTENT === This response contains all available snippets from this library. No additional content exists. Do not make further requests.