Documentation
Sign inGet started

bird email stats by-sending-ip

Usage

Exemple de code
bird email stats by-sending-ip [flags]

Description

Delivery and bounce stats grouped by sending IP, with deferral counts alongside them. sort=bounces.block surfaces reputation-damaged IPs first. Engagement, accepted, and processed counts aren't available per IP, and complaint and out-of-band bounce counts always read 0 here. For workspace-wide figures, use bird email stats daily.

Examples

Exemple de code
bird email stats by-sending-ip

Options

NameDescription
--categoryNot supported on breakdown endpoints. Supplying it returns 422. To compare categories, use GET /v1/email/stats/categories. The summary, daily, and hourly statistics accept category as a filter.
--fromStart date (inclusive) in YYYY-MM-DD, interpreted as a calendar day in timezone (a UTC day when timezone is omitted). It defaults to 30 days before to when you leave it out. When include_trend=true and trend_grain=hourly, that default tightens to 29 days before to instead, so the defaulted window still fits inside the 720-hour trend cap.
--include-trendWhen true, each row also gets a trend array: a short per-bucket series showing that IP's delivery rates over the window. A trend point's open and click rates read 0 in a bucket that had deliveries and null in one that had none, because a sending IP has no engagement data. This only works when limit is 50 or fewer and the window is at most 90 days for trend_grain=daily or 720 hours for trend_grain=hourly. Ask for more and you get a 422. When you leave from out and use trend_grain=hourly, the default window tightens to 29 days before to (720 hours total), so a request built entirely from defaults always fits inside the cap.
--limit <n>Maximum number of IP rows to return, ranked by the sort field descending.
--response-schemaPrint the fields this command returns, then exit
--sortMetric to rank IPs by, applied descending. Sorting by bounces.block puts the IPs whose reputation is most likely degraded at the top. A row whose rate is undefined because its denominator is zero sorts last. It defaults to delivered. A sending IP has no engagement, so engagement metrics aren't sortable here, and neither are processed, rejected, or oob_bounces. Possible values: delivered, bounced, complained, deferred, bounces.hard, bounces.soft, bounces.admin, bounces.block, bounces.undetermined, delivery_rate, bounce_rate, complaint_rate, bounces.hard_rate, bounces.soft_rate, bounces.admin_rate, bounces.block_rate, bounces.undetermined_rate.
--timezoneIANA timezone identifier (for example Asia/Kathmandu) to report in; defaults to UTC. Day and hour boundaries and the default window when from and to are omitted both follow it, so a calendar-day from or to names a local day. A from or to carrying its own UTC offset is rejected while this is set: pass a calendar day or a Z instant.
--toEnd date (inclusive) in 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.
--trend-grainBucket grain for the trend series. Has no effect unless include_trend=true. Possible values: daily, hourly.
NameDescription
bird email stats by-bounce-codeBounces by SMTP error code
bird email stats by-broadcastStats by broadcast
bird email stats by-categoryStats by category
bird email stats by-clientEngagement by email client
bird email stats by-complaint-typeComplaints by type
bird email stats by-locationEngagement by location
bird email stats by-mailbox-providerStats by mailbox provider
bird email stats by-mailbox-provider-regionStats by mailbox provider region
bird email stats by-recipient-domainStats by recipient domain
bird email stats by-sending-domainStats by sending domain
bird email stats by-tagStats by tag
bird email stats by-templateStats by template
bird email stats dailyDaily sending statistics
bird email stats hourlyHourly sending statistics
bird email stats summaryAggregate stats summary