Xano Documentation
Ask or search…
K

API Request History

See your incoming External API Requests in Xano
From the dashboard, easily view the high-level statistics of the API request history from your entire Workspace. You can toggle between your database and top API requests to see which of your API endpoints are being hit the most. To the right, visualize your API request history with a graph displaying the statistics of the past 24 hours. Select 'View Request Details' to see a detailed view and history of each API call made in your Workspace.
You can expand each individual call to review detailed information including inputs, response and request headers, and the output. You can even drill-down on a per-user basis to see the activity of each user in your application. Furthermore, you can view failed API calls here in order to help debug what went wrong. Finally, you can use these details to understand Webhook payloads to make it easier to build API endpoints that receive Webhooks.
You can also choose whether to see the request history for the specific branch you have active, or all branches, and download your request history as a CSV. If you would like to access your request history via API, you can do so using our Metadata API.
It doesn't stop at the entire Workspace level. From each API group, you can see the detailed history of the entire group. And from each API endpoint, you can see the history of the individual endpoint.

Function Request History

Custom Functions are similar to API endpoints in Xano, in the sense that they have the same No-Code API builder UI. However, custom functions can only be called by other internal function stacks in Xano whether that's an API, other function, or background task.
Functions also have a request history for any time a function is part of a live API request.
First, open the request history of a function from the top right menu icon.
Open request history for a function
Once opened, you can see all the requests from the past 24 hours.
At the top, you can filter the requests by the time they occurred up until and by the duration of the how long the function took to run.
The duration filter can be useful for identifying potential performance issues.
You can click on any of the requests to see the specific details of the inputs, output (response), and the function stack run time information.
Granular information on the function request.

Disabling Request History

You can disable the request history for any specific API or function from the function stack's settings.
Disabling request history can be an important step in managing your backend, as request history does utilize your database storage.
Last modified 1mo ago