Get daily inbound SMS statistics
/v1/sms/stats/inbound/dailyconst stats = await bird.sms.stats.inbound.daily({ from: "2026-05-01", to: "2026-05-31" });
for (const point of stats.data ?? []) {
console.log(point.bucket, point.received);
}stats = client.sms.stats.inbound.daily(from_="2026-05-01", to="2026-05-31")
for point in stats.data or []:
print(point.bucket, point.received)series, err := client.Sms.Stats.Inbound.Daily(context.Background(), bird.SmsStatsInboundDailyParams{
From: time.Now().AddDate(0, 0, -7),
To: time.Now(),
})
if err != nil {
log.Fatal(err)
}
for _, point := range *series.Data {
fmt.Println(*point.Bucket, *point.Received)
}$inboundDaily = $bird->sms->stats->inbound->daily(['from' => '2026-05-01', 'to' => '2026-05-31']);
foreach ($inboundDaily->getData() ?? [] as $point) {
echo $point->getBucket(), ' ', $point->getReceived(), PHP_EOL;
}bird sms stats inbound dailycurl -X GET "https://us1.platform.bird.com/v1/sms/stats/inbound/daily" \
-H "Authorization: Bearer $TOKEN"{
"period": {
"from": "2026-05-01",
"to": "2026-05-31",
"grain": "day",
"data_as_of": "2026-05-25T14:03:10Z"
},
"data": [
{
"bucket": "2026-05-01",
"received": 128
}
]
}
Returns the number of messages your numbers received, one row per calendar day. Rows use the time the carrier received each message, and days with no messages contain a zero count.
Each row contains only a count because a received message has one state. Use the outbound statistics endpoints for lifecycle and delivery-latency data about messages you send.
The maximum window is 365 days; a longer range returns 422. Set timezone to bucket rows by your local calendar day instead of UTC.
Query Parameters
fromstringStart date (inclusive), YYYY-MM-DD. Interpreted as a calendar day in timezone (a UTC day when timezone is omitted). Defaults to 30 days before to when omitted.
tostringEnd date (inclusive), YYYY-MM-DD. Interpreted as a calendar day in timezone (a UTC day when timezone is omitted). Defaults to today in that timezone when omitted. Window may not exceed 365 days.
timezonestringIANA timezone identifier used to group statistics, for example Asia/Kathmandu. The default is UTC. Day and hour boundaries, including the default window when from and to are omitted, follow this timezone. When this parameter is set, pass from and to as calendar days or Z instants instead of timestamps with explicit UTC offsets.
Response Payload
periodThe window and bucket grain the response covers, echoed from the request, plus the freshness boundary the data is current to.
Show child attributes
period.fromInclusive start of the window. A calendar day (YYYY-MM-DD) on the day grain, an RFC 3339 instant rounded to the hour on the hour grain.
period.toInclusive end of the window. A calendar day (YYYY-MM-DD) on the day grain, an RFC 3339 instant rounded to the hour on the hour grain.
period.grainThe bucket grain of the series, either day or hour.
Possible values: day, hour
period.data_as_ofLatest time reflected in the statistics. More recent events might not be included yet. Null when the freshness boundary is unavailable.
dataOne row per bucket (day or hour, per the grain) in the period, in chronological order. Buckets with no activity are included with a count of zero, so the series charts continuously without client-side gap handling.
Show child attributes
data.bucketStart of the bucket this row covers, as a calendar day (YYYY-MM-DD) for the daily series or an hour boundary (RFC 3339) for the hourly one.
data.receivedDistinct messages received in this bucket, counted by the time the carrier received them.
Related resources
Continue with the documentation, guides and examples for this topic.