API token authentication

Every documented API operation is authenticated. Send the dashboard API token in the Authorization header:

Authorization: Bearer YOUR_API_TOKEN

Create or reset a token

1. Sign in to the LTESocks dashboard.
2. Open Settings → Profile.
3. Locate API Token.
4. Create the token, or reset it when rotating credentials.
5. Copy the new value immediately and store it as a secret.

Resetting the token invalidates the previous value. Update all server-side integrations before or immediately after rotation.

Server-side use only

Treat the token like an account password:

• inject it through an environment variable or secret manager;
• use HTTPS and validate TLS certificates;
• redact Authorization from application and proxy logs;
• never expose the token in client-side JavaScript;
• use a separate deployment secret for each environment;
• rotate it after any suspected disclosure.

Compatibility

The service contains a compatibility bridge for older token formats. New integrations should always use the documented Bearer header.

Authentication failures

A missing, invalid, expired, or reset token returns a non-success response. Handle 401 as a permanent credential failure: stop retries, alert the operator, and replace the secret. Do not automatically regenerate tokens from application code.