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

# API logs

> Every call your apps have made to Pila, with the status code each returned.

API Logs records every call your apps make to Pila. When an endpoint behaves differently from what the reference describes, this is where you confirm what was actually sent and what came back.

<Frame caption="The API Logs page">
  <img src="https://mintcdn.com/dojah-9b16f14e/gbqe8nXs4Wupm4KV/images/dashboard/api-logs.png?fit=max&auto=format&n=gbqe8nXs4Wupm4KV&q=85&s=52ef48c433fc0532f1defead3f3d35e5" alt="API logs page showing call counts and a log table" width="1024" height="540" data-path="images/dashboard/api-logs.png" />
</Frame>

| Card | Meaning |
| - | - |
| **APIs Created** | The number of API calls in the selected period. |
| **Successful API Calls** | Calls that completed without an error. |
| **Failed API Calls** | Calls that returned an error. |

## Filtering

The page opens filtered to the **Last 7 days**.

* Select **+** on a chip to filter by **Date**, **Apps**, **Mode**, **Status Code** or **Services**.
* Select **×** to remove one filter, or **Clear all** to remove them all.
* Select **What do these codes mean?** for an explanation of each status code.
* Select **Export** to download the logs.

Each row shows the app name, mode, service, date/time and status.

<Note>
  If you see "No results found", no calls match your filters. Widen the date range, remove a filter, or check you are in the right mode.
</Note>

## Using logs for support

<Tip>
  Before opening a support request, find the failing call here and note the endpoint, timestamp and status code. Those three details are usually enough for the team to trace it. See [Support](/support).
</Tip>

<Warning>
  Logs contain customer data. Do not screenshot a full payload into a chat or ticket — quote the endpoint, status code and reference instead, and mask identifiers like BVNs as `*8901`.
</Warning>

## Reading status codes

| Code | Meaning |
| - | - |
| `200` | The request succeeded. |
| `400` | Something in the request was invalid. Fix it — retrying will not help. |
| `401` | Missing or wrong credentials. Check the `Authorization` and `AppId` headers. |
| `403` | Not permitted for this app or mode. |
| `404` | The resource does not exist. |
| `429` | Too many requests. Back off and retry with exponential delay. |
| `5xx` | A problem on Pila's side or an upstream provider's. Safe to retry with backoff. |

See [Response format](/api-reference/core-concepts/response-format) for the full picture, including why a `200` on a transfer does not mean it settled.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.