Technical Specifications

Authorized Server Regions

The Lizaro infrastructure operates across five primary geographic regions. Partners must direct API traffic to the region endpoint nearest to their primary user base to minimize latency and comply with data residency requirements. Cross-region fallback is handled automatically by the routing layer.

Connectivity Protocols

All partner connections to the Lizaro infrastructure must use the following approved protocols. Connections using deprecated or non-approved protocols will be rejected at the network perimeter.

API Endpoints

The Lizaro REST API follows OpenAPI 3.1 specification. All endpoints return JSON (UTF-8). The base URL for all requests is https://api.lizaro.com/v4 (or the region-specific equivalent).

Sample Request

GET /v4/resources/list HTTP/2
Host: api-eu.lizaro.com
Authorization: Bearer eyJhbGciOiJSUzI1NiIsInR5cCI6IkpXVCJ9...
Accept: application/json
X-Partner-ID: prt_a1b2c3d4e5f6
X-Request-ID: req_20260428_001

HTTP/2 200
Content-Type: application/json; charset=utf-8
X-RateLimit-Remaining: 498
X-RateLimit-Reset: 1745836800

{
  "status": "ok",
  "count": 42,
  "resources": [
    { "id": "res_logo_primary", "type": "logo", "format": "svg", "version": "4.2" },
    { "id": "res_font_inter",   "type": "font", "format": "woff2", "version": "3.19" }
  ]
}

Authentication

The Lizaro API uses OAuth 2.0 with PKCE for all partner authentication flows. Access tokens are short-lived (3600 seconds) and must be refreshed using the provided refresh token. Client credentials flow is available for server-to-server integrations.

POST /v4/auth/token
Content-Type: application/x-www-form-urlencoded

grant_type=client_credentials
&client_id=YOUR_CLIENT_ID
&client_secret=YOUR_SECRET
&scope=resources:read
       integration:write

Rate Limits

Rate limits are enforced per partner identifier at the API gateway level. Limits are applied on a rolling 60-second window. Partners exceeding their allocated rate will receive a 429 Too Many Requests response with a Retry-After header.

Rate Limit Response Headers

X-RateLimit-Limit: 500
X-RateLimit-Remaining: 487
X-RateLimit-Reset: 1745836860
X-RateLimit-Window: 60
Retry-After: 23

Environment Parameters

The following environment variables and configuration parameters must be set within the partner's integration environment prior to initiating any API connections.

TLS Configuration

All connections to Lizaro infrastructure must use TLS 1.3. The following cipher suites are supported. Partners should configure their HTTP clients to prefer the listed suites in the order shown.

IP Allowlist

Partners operating behind strict egress firewalls should allowlist the following IP ranges to ensure uninterrupted connectivity to Lizaro API infrastructure. Ranges are updated quarterly; subscribe to the System Log for change notifications.

SLA & Uptime Commitments

Lizaro infrastructure SLAs are defined per partner tier. The following table outlines the uptime commitments, response time targets, and incident notification windows applicable to each tier.

SDK & Client Library Support

Official Lizaro SDK packages are available for the following runtime environments. All SDKs implement automatic token refresh, retry logic with exponential backoff, and structured error handling.