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.
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.
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.
Using logs for support
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. 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.
Reading status codes
See Response format for the full picture, including why a 200 on a transfer does not mean it settled. 
