Overview
The API Logs page shows you what’s happening with your API activity in real time, across your account. It’s built to give you peace of mind so you can quickly see what’s working, spot issues early, and understand how your systems are communicating.
Logs are kept for 7 days and include:
Successful requests
Failed requests
Detailed logs for each request
Full request and response payloads
You can use this page to check if requests were delivered successfully, look into any errors, and keep track of activity across your connected services all from one simple view.
Accessing the API Logs Page
From the left-hand menu, look for Developers.
Click on Developer Tools > API Logs
Components
1. Summary: 'Your recent activity'
These metrics gives you instant visibility to your API usage.
Shows the overall numbers for the selected date range:
Total requests: All API requests made.
Successful: Requests returning 200 and 201 statuses
Failed: Requests returning 400,401,403,404 and 50 statuses
2. Search, Filters & Apply
The Search and Filters feature helps you quickly find the logs you’re looking for. You can search by keywords, filter by status, or narrow down by date to focus on the requests that matter most.
This functionality applies to the four pages of logs that are initially loaded. To search or filter through more records, simply load additional pages by clicking the next pages, your search and filters will then apply to the newly loaded logs as well.
Search
Type in full or partial words, and the search will look through all of the following fields to help you quickly find what you need.
Here are the possible search options:
API Endpoint: The specific API path being called.
Request ID: A unique identifier automatically assigned to each API request.
Source: Where the request originated (e.g., API, dashboard, subaccount).
Body: The content of the request, including message text and parameters.
Country: The destination country of the message based on the recipient number.
Sender ID: The "from" value used when sending the message (alphanumeric or number).
Response Code: The system’s numeric code returned after processing the request.
Response Message: A brief message explaining the response code.
Error code: the HTTP status of the call
Error Message: A short explanation of what caused the error.
Message ID: The unique identifier for the individual message once queued or sent.
Filters
Status: Filter by success, client errors, or server errors.
Endpoint: Filter by e.g.,
/v3/sms/send,/v3/mms/send,/v3/sms/history, etc.Subaccount: By default, it will be your subaccount.
Date range: We only keep the logs for 7 days You can select from these options:
Today
Last 12 hours
Last 24 hours
2 days ago
3 days ago
4 days ago
5 days ago
6 days ago
“Note: When you use the ‘2 days ago’ filter, it will show all logs from the past two days, including today.
Buttons
Clear filters: Resets all filters including the Search.
Apply: Use this to apply your current filters and search. You can either click ‘Apply’ or just press Enter to run the search.
3. Logs Table
Displays all API requests based on your filters. Columns include:
Use this table to quickly scan activity or identify failing calls.
Sorting:
You can sort by any column such as Timestamp or Status.
Clicking a column header toggles between ascending and descending order.
This helps you group errors, recent activity, or specific endpoints more efficiently.
Interactions:
Clicking a row opens full request details on the right panel.
Pagination lets you browse through all logs and loads next data.
Refresh table reloads the latest logs.
Sorting sort
Detailed Log Panels (Metadata, Request and Response Panels)
When you select a row, the full details appear.
Metadata Panel includes:
Method
Status
Message status (e.g., 200 Success)
Request ID
Subaccount
Timestamp
Client IP address
User agent
This section helps identify where the request came from (Postman, server, browser, etc.).
Request Body
Shows the exact payload sent. Useful for:
Debugging malformed JSON
Verifying parameters
Checking authentication methods
Response Body
Shows the exact response returned. Includes:
HTTP codes
Error messages
Internal response codes
Delivery data and pricing (if applicable)
This is your main tool for troubleshooting issues like failures, message errors, or incorrect payloads.
Common Use Cases
1. Debugging Failed API Calls
Open filter Status dropdown
Click a row with 400 or 500.
Review:
Response body (error message)
Request body (incorrect fields?)
Endpoint used
Subaccount that triggered it
2. Confirming SMS/MMS Was Sent Successfully
Filter endpoint
/v3/sms/send.Check status 200.
Inspect response body →
Message queued for delivery.
3. Reproducing or Escalating Issues
Copy request/response bodies directly when reporting issues.
Tips
Use Search to quickly find logs for a specific phone number or keyword.
For recurring issues, compare multiple logs side-by-side.
Logs refresh automatically when Refresh table is clicked.
Use the response payload to understand pricing or delivery issues.
FAQS
What is the API Logs page?
What is the API Logs page?
The API Logs page allows developers to view and monitor all API requests made through their account. It helps in tracking request activity, identifying errors, and debugging integrations in real time.
What information can I see in the API logs?
What information can I see in the API logs?
Each log entry includes key details such as:
Timestamp – When the request was made
Endpoint – Which API endpoint was called
Status – Whether the request succeeded or failed
Response Code – HTTP status code (e.g., 200, 400, 500)
Request ID – A unique identifier for each request
What are the “All,” “Success,” and “Failed” counters?
What are the “All,” “Success,” and “Failed” counters?
These counters summarize your API request activity:
All – Shows the total number of API calls made
Success – Shows the count of successfully completed requests
Failed – Shows the count of requests that resulted in an error
How does pagination work on the logs page?
How does pagination work on the logs page?
Logs are displayed in pages to make browsing faster and easier.
Use the pagination controls (e.g., Next, Previous, or numbered pages) to navigate through your log history.
What does the “Refresh” button do?
What does the “Refresh” button do?
The Refresh button reloads the logs table to show the most recent API activity without reloading the entire dashboard.
This is useful when monitoring live API requests.
How often are logs updated?
How often are logs updated?
Logs are updated in near real time. You can manually click Refresh to get the latest data instantly.
How far back can I view API logs?
How far back can I view API logs?
You can view logs from the past 7 days.
Older logs may be archived or deleted automatically.
Can I export my API logs?
Can I export my API logs?
Currently, export functionality may not be available directly on the page.
Can I search or filter my API logs?
Can I search or filter my API logs?
Yes. You can filter logs by:
Status (Success, Failed)
Date range
Endpoint
Search - type any keyword
What should I do if a request failed?
What should I do if a request failed?
You can:
Click the failed log entry to view details and error messages
Check the response code and error body
Use this data to troubleshoot your API integration
Who can access the API Logs page?
Who can access the API Logs page?
Account and subaccount can access and view their API logs. This release, it is developed that subaccounts can only view theirs.