Stop guessing, start debugging with API Logs

Every API call in your integration is a point of friction, a potential black box that can bring your development sprint to a halt. True velocity isn’t just about writing code; it’s about removing that friction.

That's why we built the new API Logs page.

It’s designed around a single principle: less time debugging is more time building. We've turned your API history into a high-performance diagnostic tool, giving you the clarity needed to resolve issues instantly and ship with unshakeable confidence.

Let's explore how this changes your workflow.

Why do you need API logs for an SMS tool?

Developers rely on logs. They are like the heartbeat of applications.

And they’re especially important when integrating a critical communications service like ClickSend for SMS and MMS for your own software or a business.

When there’s a communication breakdown or you just want to check that everything is working, having a transparent and detailed view of every API call is essential for debugging, monitoring, and auditing. An API Logs page is your mission control for monitoring all API activities (and making sure messages are reaching their destinations).

Want to see ClickSend’s API Logs page in action? Sign up for a trial and set up some API calls using your trial credit.

How does ClickSend’s API log tool work?

Want to know how the ClickSend API Logs function works on our platform? Here’s a deep dive on the key features.

1. Activity summary metrics

At the top of the page, you are presented with key statistics summarising your API usage. This data helps you gauge the volume and success rate of your recent operations.

• Total Requests: The cumulative count of all API calls made.

• Successful: The number of requests that resulted in a success status (typically HTTP 200 series).

• Failed: The number of requests that resulted in an error status (e.g., HTTP 400 or 500 series).

• Log Retention: Logs are typically retained for 7 days.

2. Log table functionality

The main section is a filterable table listing every API transaction.

Filtering and search

You can use controls above the table to efficiently locate specific entries:

• Search - users can search by following fields and categories. (see table below)

• Status Filter: View only successful or specific error code requests. Status filter options are:

  • All success statuses

  • All error statuses, 200 ok, 201 created, 400 bad request, 401 unauthorised, 403 Forbidden, 404 not found and 500 internal server error.

• Endpoint Filter: Restrict the view to calls made to a specific API path (e.g., /v3/sms/send).

• Timeframe: Adjust the time window of the logs displayed (e.g., Last 24 Hours).

Key columns

The table displays essential data points for each call:

• Status: The HTTP status code returned.

• Method: The HTTP method used (e.g., POST, GET).

• Endpoint: The target API resource path.

• Timestamp: The time the request was processed.

3. Detailed request and response analysis

Selecting an entry from the table reveals a detailed panel, which contains diagnostic information crucial for troubleshooting.

Request and Response Information (the Metadata)

This section confirms the outcome and environment of the API call and the message call:

• Status: Confirms the status of the API call.

• Message Status: Confirmed the status of the message.

• Request ID: A unique identifier for the transaction.

• Timestamp: The precise time of the event.

• Client IP Address and User Agent: Identifiers for the originating system.

Request body

The Request Body section displays the exact payload (e.g., JSON) that your application sent to the ClickSend API. This is vital for confirming correct data formatting, parameters, and content (e.g., the message text and recipient number for an SMS).

By providing comprehensive metrics, filtering capabilities, and detailed request data, the API Logs page offers the necessary tools for routine monitoring and issue resolution within the ClickSend environment.

Response body

While the HTTP Status Code (like 200 or 400) tells you if the request succeeded or failed generally, the Response Body provides the ClickSend platform's definitive message on what happened. This section is usually displayed below the Request Body in the detailed log view.

The Response Body is typically a JSON object that follows a consistent structure, containing three main pieces of information:

A. HTTP Status Confirmation (http_code)

This is the standard HTTP status code returned to your application. For a successful request to process data (like sending a message), this is almost always 200.

B. ClickSend Response Code (response_code)

This is the internal status code from the ClickSend platform itself.

• Success: This will typically be SUCCESS, confirming the message has been accepted and queued for delivery.

• Failure: For a failed request, this field provides a specific, detailed code that helps pinpoint the problem (e.g., MISSING_CREDENTIALS or a code for an invalid recipient number).

C. Data Payload (data)

For successful calls, the data object contains the transactional details you need to confirm the operation:

For successful message sends (/v3/sms/send): This payload includes crucial identifiers for tracking:

• message_id: The unique ClickSend ID assigned to the message(s), which you need to track delivery reports (DLRs).

• currency: Information on the currency used for billing.

• message_price: The cost of the transaction.

• For requests retrieving data (eg. GET endpoints): This section contains the actual resource you requested, such as a list of your contacts, history records, or account balance.

Ready to build with an SMS tool for devs?

When something breaks, you shouldn’t have to dig through guesswork or partial data.

With ClickSend’s API Logs, you get a clear, real-time window into exactly what your SMS and MMS API calls are doing — so you can debug faster, deploy with confidence, and keep messages moving.

If you’re ready to build on a messaging platform designed for developers, start a free ClickSend trial and watch your first API calls come to life in the Logs.