Get message log
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.
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
id
Unique ID of the log.
Response
The request has succeeded.
id
A unique identifier for the log.
from
The origin phone number.
to
The destination phone number.
status
The status of the message.
direction
The direction of the message.
kind
The kind of message.
source
Source of this log entry.
type
Type of this log entry.
url
URL for the resource associated with this log entry. Null for Relay messages.
number_of_segments
The number of segments.
charge
The charge in dollars.
charge_details
Details on charges associated with this log.
created_at
Date and time when the message entry was created.
error_message
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_code
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