The API Dashboard includes a real-time request log that shows every API call made with your key. Use it to monitor usage, debug integration issues, and track your rate limit consumption.
Accessing the Request Log
Log in to your Bouncy.ai account.
Click API in the left sidebar to open the API Dashboard.
Scroll down past the usage stats to find the Request Log section.
Usage Statistics
Above the request log, three summary cards show your current usage:
Stat | Description |
Requests Today | The number of API requests made since midnight (UTC). Shows remaining requests against your daily limit. |
Requests This Hour | The number of API requests made in the current hour. Shows remaining requests against your hourly rate limit. |
Total Requests | The all-time total number of API requests made with your key. |
Each card includes a progress bar showing how much of your limit has been used.
Reading the Request Log
The request log displays API calls in a table-like format with the following columns:
Column | Description |
Timestamp | The date and time of the request in |
Method | The HTTP method used (GET, POST, PUT, DELETE, PATCH). Each method is colour-coded: |
- GET: green | |
- POST: blue | |
- PUT: amber | |
- DELETE: red | |
- PATCH: purple | |
Endpoint | The API endpoint that was called. |
Status | The HTTP status code of the response. Colour-coded: |
- 2xx (success): green | |
- 429 (rate limited): amber | |
- 4xx/5xx (error): red | |
Response Time | How long the request took to process, displayed in milliseconds (ms). |
Log Controls
At the bottom of the request log, you have several controls:
Display Limit
Choose how many log entries to show at once:
10 -- Quick overview of recent requests (default).
100 -- A broader view of recent activity.
1000 -- Full history for deeper analysis.
Click the number button to switch. The currently selected limit is highlighted.
Refresh
Click the Refresh button to reload the log with the latest data. The log scrolls to the top after a refresh.
Infinite Scroll
As you scroll down through the log, additional entries load automatically when you reach the bottom. A loading indicator appears while more entries are being fetched. When all entries have been loaded, you will see "No more requests to load."
Using Logs for Debugging
The request log is helpful for troubleshooting API integration issues:
Check status codes -- A 401 status means your API key is invalid or missing. A 429 means you have hit your rate limit.
Monitor response times -- If response times are unusually high, it may indicate a network issue or a particularly complex request.
Verify endpoints -- Confirm that your application is calling the correct endpoints with the expected methods.
Track rate limits -- Watch the "Requests This Hour" counter to stay within your plan's rate limit.
Documentation
For full details on available API endpoints, request formats, and response structures, visit the documentation:
Related Articles