---
title: "Get Responses by Time Frame"
method: GET
path: "/get-user-sms-responses.json"
tags: ["SMS"]
---

# Get Responses by Time Frame

`GET /get-user-sms-responses.json`

## Request

- Base URL: `https://api.transmitsms.com`
- URL: `https://api.transmitsms.com/get-user-sms-responses.json`
- Auth: HTTP basic

Gets the messsages from a defined timeframe.

## Pagination

This endpoint supports pagination using the page/max pattern:

**Parameters:**
- `page`: Page number starting from 1 (default: 1)
- `max`: Maximum results per page (default: 10, recommended: 10-100)
- `mobile`: Required mobile number filter (E.164 format)
- `start`/`end`: Optional date range filters

**Response Structure:**
The response includes pagination metadata:
- `page.count`: Total number of pages available
- `page.number`: Current page number
- `total`: Total count of SMS responses matching the filters

**Navigation Examples:**
```
# First page of responses for a mobile number (default)
GET /get-user-sms-responses.json?mobile=61478038915

# Second page with 25 results per page
GET /get-user-sms-responses.json?mobile=61478038915&page=2&max=25

# Responses within date range with pagination
GET /get-user-sms-responses.json?mobile=61478038915&start=2020-04-01T00:00:00Z&end=2020-04-30T23:59:59Z&max=50

# Navigate through all pages
GET /get-user-sms-responses.json?mobile=61478038915&page=1&max=20
GET /get-user-sms-responses.json?mobile=61478038915&page=2&max=20
# Continue until page.number >= page.count
```

**Best Practices:**
- Use max=10-25 for UI display of conversation history
- Use max=50-100 for data export or analysis tasks
- Always specify date ranges for large datasets to improve performance
- Check page.count to determine if more pages exist
- Use sorting parameters (sort_field, order) to organize results effectively
- Consider the mobile number is required - this endpoint is designed for per-contact message history

## Query parameters

- `mobile` integer, required
- `countrycode` string
- `start` string, date-time
- `end` string, date-time
- `sort_field` string
- `order` string
- `page` integer
- `max` integer

## Response `200`

OK

- object
  - `id` integer: Numeric ID assigned to the message received.
  - `message_id` integer: Numeric ID assigned to the message that was responded to.
  - `list_id` integer: Numeric ID of the list that the original message was sent to. Returns 0 if message was not sent to a list.
  - `received_at` string, date-time: Date and time that response was received to your account. Returned in ISO8601 format YYYY-MM-DD HH:MM:SS in UTC Timezone.
  - `first_name` string: First name of responder. Retrieved from list contact if available.
  - `last_name` string: Last name of responder. Retrieved from list contact if available.
  - `msisdn` integer: Mobile number of responder.
  - `error` object: Error messages related to this call. For general errors see the API Introduction. | CODE | HEADER | DESCRIPTION | |----------------|--------|------------------------------------------------------------| | FIELD_INVALID | 400 | If you provide 'keyword', you must provide 'number' | | FIELD_INVALID | 400 | Field "keyword_id" has wrong type, expected type - numeric | | NO_ACCESS | 400 | You do not have access to this ‘message’ |
    - `CODE` integer: Error code.
    - `HEADER` integer: HTTP status code.
    - `DESCRIPTION` string: Description of the error.

## Changes

- **2026-11-03** `486bd23529d2`: 1 info
  - endpoint added

[Operation history](https://skmtc.dev/kudosity/apis/transmit-sms-api/changes/get-user-sms-responses.json/get.md)

---

[API](https://skmtc.dev/kudosity/apis/transmit-sms-api.md) - [All operations](https://skmtc.dev/kudosity/apis/transmit-sms-api/llms.txt) - [OpenAPI document](https://skmtc.dev/kudosity/apis/transmit-sms-api/revisions/486bd23529d2?raw)