Get Outbound SMS Message Logs
Query
Mobile Country Code.
Mobile Network Code. Mobile Country Code is required if this property is used.
The sender ID which can be alphanumeric or numeric.
Message destination address.
Unique ID assigned to the request if messaging multiple recipients or sending multiple messages via a single API request. May contain multiple comma-separated values. Maximum length 2048 characters.
Unique message ID for which a log is requested. May contain multiple comma-separated values. Maximum length 2048 characters.
The logs will only include messages sent after this date. Use it alongside sentUntil to specify a time range for the logs, but only up to the maximum limit of 1000 logs per call. Has the following format: yyyy-MM-dd'T'HH:mm:ss.SSSZ.
The logs will only include messages sent before this date. Use it alongside sentSince to specify a time range for the logs, but only up to the maximum limit of 1000 logs per call. Has the following format: yyyy-MM-dd'T'HH:mm:ss.SSSZ.
Maximum number of messages to include in logs. If not set, the latest 50 records are returned. Maximum limit value is 1000 and you can only access logs for the last 48h.
Entity id used to send the message. For more details, see our [documentation](https://www.infobip.com/docs/cpaas-x/application-and-entity-management).
Application id used to send the message. For more details, see our [documentation](https://www.infobip.com/docs/cpaas-x/application-and-entity-management).
ID of a campaign that was sent in the message. May contain multiple comma-separated values.
Flag used to enable cursor-based pagination. When set to true, the system will use the cursor to fetch the next set of logs.
Value which represents the current position in the data set. For the first request, this field shouldn't be defined. In subsequent requests, use the `nextCursor` value returned from the previous response to continue fetching data.
Comma-separated response fields to include.