> ## Documentation Index
> Fetch the complete documentation index at: https://docs.notifique.dev/llms.txt
> Use this file to discover all available pages before exploring further.

# API logs

> Query HTTP call history to audit integrations and debug errors.

<Tip>
  API logs are your **integration statement**: each HTTP call with request, response, and status — ideal for debugging 401, 403, and 400.
</Tip>

## What are they?

History of **all API calls** in the workspace: method, endpoint, body (masked), response, and duration.

Like a bank statement: it does not show whether the message reached the customer, but every **transaction** between your system and Notifique.

## Logs vs webhooks

| Situation                      | Logs    | Webhooks |
| ------------------------------ | ------- | -------- |
| Why did the API return 403?    | **Yes** | No       |
| Which key made the call?       | **Yes** | No       |
| Message delivered to customer? | No      | **Yes**  |
| Real-time reaction             | No      | **Yes**  |

## Query via API

Scope: `logs:read`.

```bash theme={null}
curl "https://api.notifique.dev/v1/logs?limit=20&status=403" \
  -H "Authorization: Bearer sk_live_..."
```

Filters: `status`, `method`, `startDate`, `endDate`, `apiKeyId`, `page`, `limit` (max 100).

## Detail by ID

`GET /v1/logs/:id` — full body, `correlationId`, API key name and prefix.

Cross-reference `code` in `responseBody` with [Error responses](/en/guides/conceitos/resposta-de-erros).

## Next steps

* [Webhooks](/en/platform-api/como-funciona/webhooks)
* [Scopes](/en/platform-api/como-funciona/escopos-api-key): add `logs:read` to the key