Answer: A 401 Unauthorized error means the API key is invalid or missing, and you fix it by verifying your API key in the Authorization header. A 402 Payment Required error means insufficient credits, fixed by adding credits at app.cline.bot, and a 403 Forbidden error means the key does not have access to this resource, fixed by checking key permissions. Status: Confirmed Entry: tool/cline/troubleshooting/http-error-codes Revision: 1 Digest: sha256:900a664461ed5719 (changes whenever the content changes) Timeline: Created: 2026-11-13T03:06:13Z Last changed: 2026-11-13T03:06:13Z Last verified: 2026-11-20T12:26:34Z Next check: 2026-11-21T12:26:34Z Check interval: Daily Expected change: No fixed schedule Data: Field | Value | Source | As of 401 cause | Invalid or missing API key | [1] | 2026-11-20 401 fix | Verify your API key in the `Authorization` header | [1] | 2026-11-20 402 cause | Insufficient credits | [1] | 2026-11-20 402 fix | Add credits at [app.cline.bot](https://app.cline.bot) | [1] | 2026-11-20 403 cause | Key does not have access to this resource | [1] | 2026-11-20 403 fix | Check key permissions | [1] | 2026-11-20 Sources: [1] Cline. "Errors". https://docs.cline.bot/api/errors.md Role: primary. Accessed: 2026-11-20T12:26:34Z Quote: "| `401` | Unauthorized | Invalid or missing API key | Verify your API key in the `Authorization` header |" (Supports: 401 cause, 401 fix) Quote: "| `402` | Payment Required | Insufficient credits | Add credits at [app.cline.bot](https://app.cline.bot) |" (Supports: 402 cause, 402 fix) Quote: "| `403` | Forbidden | Key does not have access to this resource | Check key permissions |" (Supports: 403 cause, 403 fix) Published: 2026-11-20T06:01:38Z Snapshot SHA-256: 4d4f60088ce3ab7f7875c6a52c2dff0aa74326b41597c22c69a4777ab3fdb83d (captured 2026-11-13T03:06:13Z) Verification: Method: Automated extraction from [1] with deepseek-flash (JSON output, thinking disabled). Every value was checked by code to appear verbatim in a quoted passage of [1]. On this check the text of [1] was unchanged since 2026-11-13T03:06:13Z, so the values verified then were kept. Cross-check: not-available at 2026-11-20T12:26:34Z. No independent second source is configured for this entry Last successful check: 2026-11-20T12:26:34Z Last attempt: 2026-11-20T12:26:34Z Notes and limitations: Extracted automatically from a single official source (section "HTTP Errors"). Related: https://latestn.com/tool/cline/troubleshooting/jupyter-notebook-limitations What are the limitations of Cline's Jupyter Notebook support? https://latestn.com/tool/cline/troubleshooting/legacy-vs-current-tool-names What are the differences between legacy tool names and current runtime tools in Cline? https://latestn.com/tool/cline/troubleshooting/litellm-admin-troubleshooting How do I troubleshoot problems when configuring LiteLLM in Cline? https://latestn.com/tool/cline/troubleshooting/api-error-format What error format does the Cline API return for errors? https://latestn.com/tool/cline/troubleshooting/bedrock-troubleshooting How do I troubleshoot AWS Bedrock connection issues in Cline? https://latestn.com/tool/cline/troubleshooting/events-not-appearing How do I troubleshoot OpenTelemetry events not appearing in Cline? https://latestn.com/tool/ All entries in AI tools Change log: Time | Event | Change | Source 2026-11-13T03:06:13Z | added | Entry created | — Changes for this entry as a feed: https://latestn.com/tool/cline/troubleshooting/http-error-codes/latest Challenge this entry: Open challenges: None How: If a value here is wrong or out of date, send what is wrong and a link to evidence. Challenges are queued and checked against the evidence; they do not change the entry by themselves. If the entry changes as a result, the change log says so. Form: https://latestn.com/dispute/tool/cline/troubleshooting/http-error-codes POST: https://latestn.com/dispute/tool/cline/troubleshooting/http-error-codes with claim, evidence_url, and optionally field and contact (form-encoded or JSON) GET: https://latestn.com/dispute/tool/cline/troubleshooting/http-error-codes?claim={what is wrong}&evidence_url={link} How to cite: LatestN. (2026). What do Cline API HTTP error codes like 401, 402, and 403 mean and how do I fix them? Revision 1, last verified 2026-11-20T12:26:34Z. https://latestn.com/tool/cline/troubleshooting/http-error-codes (accessed 2026-11-21T09:53:43Z). @misc{LatestN_tool_cline_troubleshooting_http_error_codes_r1, title = {What do Cline API HTTP error codes like 401, 402, and 403 mean and how do I fix them?}, author = {{LatestN}}, year = {2026}, howpublished = {\url{https://latestn.com/tool/cline/troubleshooting/http-error-codes}}, note = {Revision 1; digest sha256:900a664461ed5719; last verified 2026-11-20T12:26:34Z; accessed 2026-11-21T09:53:43Z} } Reuse: License: CC BY 4.0 (https://creativecommons.org/licenses/by/4.0/) Attribution: Copying and adapting are allowed, including commercially, if you credit LatestN and link to the entry you used. Each entry ends with a ready-made citation. URL: https://latestn.com/tool/cline/troubleshooting/http-error-codes