Information
- OpenAPI version:
3.0.3
Overview
LTESocks Public API 0.1.0
Section titled “LTESocks Public API 0.1.0”The documented mutation endpoints accept an Idempotency-Key UUID.
It is required for residential data purchases and optional on existing port endpoints.
Residential sub-user mutations also require a key (a non-empty string up to 255 characters).
The replay headers described below apply to endpoints using response replay middleware;
sub-user operations do not promise a cached response or these replay headers.
A replayed response has the Idempotency-Replayed: true header and preserves
response headers from the original response, including Retry-At and Retry-After.
Authentication
Section titled “Authentication”bearerAuth
Section titled “bearerAuth”Send the API token as Authorization: Bearer <token>.
Security scheme type: http
Bearer format: API token