Meltwater · Rate Limits
Meltwater Rate Limits
Meltwater limits the API on four independent axes: per-endpoint request rate, a daily analytics call budget, a monthly document allowance, and a monthly export count. The monthly and daily budgets are contract terms, not published numbers - what is published are the "inclusive API access" defaults that ship with the core Meltwater packages.
Meltwater Rate Limits is the machine-readable rate-limit profile for Meltwater on the APIs.io network, conforming to the API Commons Rate Limits specification.
It captures 7 rate-limit definitions.
Tagged areas include Media Monitoring, Social Listening, PR Analytics, Brand Intelligence, and News API.
7 Limits
Media MonitoringSocial ListeningPR AnalyticsBrand IntelligenceNews APISocial AnalyticsMedia Intelligence
Limits
Export endpoint rate limit per_endpoint
Daily analytics calls (inclusive API access) per_account
Customers with an API package have a contract number instead (Meltwater's own example is 100/day). The day window starts at the first request after the counter resets, not at midnight UTC.
Daily analytics calls (API package) per_contract
Stated in the customer contract; surfaced at runtime in the RateLimit-Day-Limit header.
Documents per month (inclusive API access) per_account
Resets on the 1st. Documents are NOT de-duplicated - exporting the same document twice costs two. Documents imported through BYOC and read back do not count.
Exports per month (inclusive API access) per_account
One export may cover up to 5 saved searches or tags and still counts as one. API package customers have a contract number (Meltwater's example is 100/month).
Documents per export per_request
An export forecast above this is randomly sampled down to approximately 2,000,000 documents.
MCP endpoint rate limit per_key
Not documented anywhere. Observed on a live unauthenticated POST to the MCP endpoint on 2026-08-13, which returned RateLimit-Limit 60, RateLimit-Remaining 59, RateLimit-Reset 55 and X-RateLimit-Limit-Minute 60 alongside the 401.