For AI agents: a documentation index is available at the root level at /llms.txt and /llms-full.txt. Append /llms.txt to any URL for a page-level index, or .md for the markdown version of any page.
Log inSign up
Support
  • Core
    • Overview
    • Authorization
    • Base URL
    • Data formats
    • Paging
    • Error codes
    • Permissions
  • Calling
  • Datasphere
  • Logs
      • GETGet message log
      • GETList message logs
  • Messaging
  • Phone Number Management
  • Platform
  • Resource Management
LogoLogoSignalWire Docs
Log inSign up
Support
LogsMessage Logs

Get message log

|View as Markdown|Open in Claude|
GET
https://{your_space_name}.signalwire.com/api/messaging/logs/:id
GET
/api/messaging/logs/:id
$curl https://{your_space_name}.signalwire.com/api/messaging/logs/id \
>     -u "<project_id>:<api_token>"
1{
2  "id": "string",
3  "from": "+12077447397",
4  "to": "+12029921413",
5  "status": "failed",
6  "direction": "inbound",
7  "kind": "sms",
8  "source": "laml",
9  "type": "relay_message",
10  "url": "https://example.signalwire.com/api/laml/2010-04-01/Accounts/c38dacad-2f6c-4de1-93d6-cc732e0c70c5/Messages/9ee38635-899a-490a-bfd1-9e72f5eea53c",
11  "number_of_segments": 1,
12  "charge": 0,
13  "charge_details": [
14    {
15      "description": "Inbound SMS",
16      "charge": 0.00415
17    }
18  ],
19  "created_at": "2024-05-06T12:20:00Z",
20  "error_message": "From number is not a SMS-capable phone number.",
21  "error_code": "21601"
22}

Find a log by ID.

Permissions

The API token used to authenticate must have the following scope(s) enabled to make a successful request: Messaging.

Learn more about API scopes.

Was this page helpful?
Previous

List message logs

Next
Built with

Authentication

AuthorizationBasic
SignalWire Basic Authentication using Project ID and API Token. The client sends HTTP requests with the Authorization header containing the word Basic followed by a space and a base64-encoded string of project_id:token. The project ID will be used as the username and the API token as the password. Example: ``` Authorization: Basic base64(project_id:token) ```

Path parameters

idstringRequiredformat: "uuid"
Unique ID of the log.

Response

The request has succeeded.
idstringformat: "uuid"
A unique identifier for the log.
fromstring
The origin phone number.
tostring
The destination phone number.
statusenum
The status of the message.
directionenum
The direction of the message.
Allowed values:
kindenum
The kind of message.
Allowed values:
sourceenum
Source of this log entry.
Allowed values:
typeenum
Type of this log entry.
Allowed values:
urlstring or nullformat: "uri"
URL for the resource associated with this log entry. Null for Relay messages.
number_of_segmentsinteger
The number of segments.
chargedouble
The charge in dollars.
charge_detailslist of objects
Details on charges associated with this log.
created_atdatetime
Date and time when the message entry was created.
error_messagestring or null

Description of the error when the message failed. Null when the message did not fail. LaML messages use the codes documented at https://signalwire.com/docs/compatibility-api/rest/error-codes.

error_codestring or null

Error code identifying why the message failed. Null when the message did not fail. Some Relay messages may have an error_message without an error_code — the error_code is a newer pattern that is not used in all Relay areas.

Errors

400
Bad Request Error
401
Unauthorized Error
404
Not Found Error
422
Unprocessable Entity Error
500
Internal Server Error

SignalWire Basic Authentication using Project ID and API Token.

The client sends HTTP requests with the Authorization header containing the word Basic followed by a space and a base64-encoded string of project_id:token. The project ID will be used as the username and the API token as the password.

Example:

Authorization: Basic base64(project_id:token)