Listrak · Rate Limits

Listrak Rate Limits

Listrak publishes a numeric rate limit for exactly one of its eight REST APIs. The Privacy REST API states 20 requests per 10 seconds and 60 requests per minute in its own spec description. The Mobile App Push and Two-Way SMS APIs declare 429 Too Many Requests as a real response on nine operations and list it in their status-code tables, but publish no number. The Email, SMS, Data Import, Cross Channel and Media APIs publish neither a number nor a 429. NO Listrak API documents a rate-limit response header of any kind - no RateLimit-*, no X-RateLimit-*, no Retry-After - so a client that hits a limit gets a status code and no runtime signal to pace against.

Listrak Rate Limits is the machine-readable rate-limit profile for Listrak on the APIs.io network, in the API Commons Rate Limits shape.

It captures 9 rate-limit definitions.

Limit state is signalled in the documented and notes response headers.

Tagged areas include Email Marketing, SMS Marketing, Marketing Automation, Cross-Channel, and Retail.

9 Limits documentednotes
Transcribed from the provider's documentation on 2026-08-13 — api.listrak.com/privacy/swagger/docs/v1.
View Source
Email MarketingSMS MarketingMarketing AutomationCross-ChannelRetailPush NotificationsData ImportPrivacyE-CommerceCustomer DataTransactional MessagingSegmentationProduct ReviewsMedia ManagementTwo-Way SMSRCS

Limits

Privacy REST API per-integration
· per 10 seconds
20/10 seconds
Privacy REST API per-integration
· per 1 minute
60/1 minute
The two windows run together - 20/10s is the burst ceiling and 60/min is the sustained ceiling, so a client cannot spend the 10-second allowance six times in a minute.
Mobile App Push API unspecified
429 "Too Many Requests - The request rate limit has been exceeded" is in the status-code table and is a declared response on all five operations (createAppPushDevice, getAppPushDevice, updateAppPushDevice, patchAppPushDevice, createMobileDeviceEngagementEvent). The threshold is not published.
Two-Way SMS Conversation API unspecified
429 is in the status-code table and is a declared response on all four operations (openTicket, closeTicket, getMessageStream, send). The threshold is not published.
Email REST API unspecified
No published limit and no 429 declared on any of the 83 operations. Payload size limits exist but are undisclosed, and exceeding them returns 404 Not Found rather than 413 - a genuine trap worth knowing about. Bulk contact loading is better done through ListImport_PostImportFileResource than by looping Contact_PostContactResource.
SMS REST API unspecified
No published API limit. Separately, SMS/MMS delivery throughput is bounded by carrier and sender code (short code) capacity and by the account's contracted send volume - a delivery constraint, not an API rate limit.
Data Import REST API unspecified
No published limit. All five operations are bulk collection POSTs (customers, orders, products, reviews, rating summaries); per-batch size caps are not published, and FTP import is offered as the alternative for large-volume ingestion.
Cross Channel REST API unspecified
Media REST API unspecified

Work with this as data

Every rate limit here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for rate limits

4 MCP tools reach this
  • find_rate_limitsBrowse and filter every rate limit in the catalog.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools →

Call it yourself

curl for this page
This rate limit 
curl "https://apis.io/api/v1/rate-limits/listrak-rate-limits"
All rate limits 
curl "https://apis.io/api/v1/rate-limits?limit=25"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have.