Requests and localization

Standard headers

Accept: application/json
Accept-Language: en
Authorization: Bearer YOUR_API_TOKEN
Content-Type: application/json

Content-Type is required when a request has a JSON body. Accept-Language is optional; the service uses en when the header is absent.

Language header

Send a supported language code, such as en. The middleware validates the supplied locale, and unsupported values can fail before the controller runs. The header influences service messages; it does not rename JSON field keys.

JSON bodies

Send valid UTF-8 JSON and use the exact field names shown in the API reference. Do not send string values for booleans or integers:

{
  "autoRenew": true,
  "autoResetInterval": 600
}

Time values

Date filters use RFC 3339-style timestamps. Include an explicit timezone when possible:

{
  "from": "2026-07-01T00:00:00Z",
  "to": "2026-07-31T23:59:59Z",
  "page": 1,
  "pageSize": 20
}

Set a finite client timeout. A 30-second total timeout is a reasonable starting point for JSON operations; VPN archive downloads may need a separate download timeout.