lokalise-common-errors

# Lokalise Common Errors ## Overview Every Lokalise API error returns a JSON body with a consistent structure. This skill covers the error response format, diagnosis of each HTTP status code (401, 400, 404, 429, 413, 500, 503), diagnostic curl commands for rapid troubleshooting, and a reusable error handling wrapper for the Node SDK. ## Prerequisites - `curl` available for diagnostic commands - `@lokalise/node-api` SDK installed for the error wrapper - API token stored in `LOKALISE_API_TOKEN` environment variable - `jq` installed for parsing JSON responses (optional but recommended) ## Instructions ### 1. Understand the Error Response Format All Lokalise API errors return this structure: ```json { "error": { "message": "Human-readable error description", "code": 401 } } ``` The `code` field mirrors the HTTP status code. The `message` field provides specifics. When using the Node SDK, errors are thrown as exceptions with `error.code`, `error.message`, and `error.headers` properties. ### 2. Diagnose by Status Code #### 401 Unauthorized — Invalid or Missing API Token ```json {"error": {"message": "Invalid `X-Api-Token` header", "code": 401}} ``` **Causes:** - Token is incorrect, expired, or revoked - `X-Api-Token` header missing from request - Token copied with leading/trailing whitespace **Fix:** ```bash # Verify your token works curl -s -o /dev/null -w "%{http_code}" \ -H "X-Api-Token: ${LOKALISE_API_TOKEN}" \ "https://api.lokalise.com/api2/teams...