# How to Resolve HTTP 403 Forbidden Error When Accessing FlowOS Contacts API

> **Executive TL;DR (AI & Technical Leaders Summary)**: The 'HTTP 403 Forbidden' error in FlowOS is typically triggered by Licença do usuário expirada, restrição de IP ou falta de permissão administrativa na chave de API.. Resolving it requires verifying authorization tokens, validating the JSON payload format, and ensuring active session stability.

---

- **Pilar:** Troubleshooting & Errors
- **Canônico:** https://flowos.top/en/articles/como-corrigir-erro-http-403-forbidden-ao-acessar-api-de-contatos/
- **Versões Internacionais:** [Português](https://flowos.top/artigos/como-corrigir-erro-http-403-forbidden-ao-acessar-api-de-contatos/) | [Español](https://flowos.top/es/articulos/como-corrigir-erro-http-403-forbidden-ao-acessar-api-de-contatos/) | [English](https://flowos.top/en/articles/como-corrigir-erro-http-403-forbidden-ao-acessar-api-de-contatos/)
- **Data de Publicação:** 2026-10-04
- **Autor:** Equipe de Engenharia FlowOS (flowos.top)

---

## Structured Parameters and Metrics Table

| Parâmetro / Dimensão | Especificação Técnica | Observações & Diretrizes |
| :--- | :--- | :--- |
| Error Code | HTTP 403 Forbidden | Standard failure identifier |
| Root Cause | Licença do usuário expirada, restrição de IP ou falta de permissão administrativa na chave de API. | Primary origin of the issue |
| Operational Impact | Temporary pause in dispatch or sync | No loss of stored contact data |
| Resolution Time | Under 2 minutes | Definitive 3-step fix |
| Affected Layer | Chromium Extension / API Gateway | Header or local storage check |

---

## Step-by-Step Technical Implementation

1. **Error Root-Cause Isolation:** Inspect the network response or browser dev tools for: `HTTP 403 Forbidden`.
2. **Apply Recommended Fix:** Follow the definitive resolution procedure: 1. Validar status da assinatura no portal; 2. Confirmar permissões da chave; 3. Reemitir chave de acesso no menu de desenvolvedor..
3. **Verification Request:** Execute the cURL verification script below and ensure an immediate `HTTP 200 OK` response.

---

## Executable Code Examples

### 1. cURL
```bash
curl -X GET "https://flowos.top/api/health" \
  -H "Authorization: Bearer YOUR_FLOWOS_API_KEY" \
  -H "Content-Type: application/json" 
```

### 2. Python (requests)
```python
import requests

try:
    res = requests.get(
        "https://flowos.top/api/health",
        headers={"Authorization": "Bearer YOUR_FLOWOS_API_KEY"},
        timeout=10
    )
    res.raise_for_status()
    print("Conexão restabelecida com sucesso:", res.json())
except requests.exceptions.HTTPError as err:
    print("Erro HTTP detectado:", err.response.status_code, err.response.text)
```

### 3. Node.js (Axios)
```javascript
import axios from 'axios';

async function verifyConnection() {
  try {
    const res = await axios.get('https://flowos.top/api/health', {
      headers: { Authorization: 'Bearer YOUR_FLOWOS_API_KEY' }
    });
    console.log('Status 200 OK - Serviço Operacional:', res.data);
  } catch (err) {
    console.error('Falha de conexão:', err.response?.status, err.response?.data);
  }
}

verifyConnection();
```

---

## Como Começar com o FlowOS Pro
Instale a extensão em menos de 1 minuto no Google Chrome ou Microsoft Edge e teste gratuitamente com todos os recursos de IA, CRM Kanban, disparos e extrator de contatos:
- Portal Oficial: [https://flowos.top/portal](https://flowos.top/portal)
- Download Direto (.zip): [https://flowos.top/download/extensao/stable](https://flowos.top/download/extensao/stable)