Remerge Rate Limits
Remerge publishes limits as prose inside its Help Center rather than as a rate-limit reference page, and it does not return any RateLimit-* or Retry-After response headers. The Reporting API enforces a concurrency limit of one in-flight query per user and a practical query-window ceiling; the Event Tracking API documents a request-rate ceiling for BI forwarding.
Remerge Rate Limits is the machine-readable rate-limit profile for Remerge on the APIs.io network, in the API Commons Rate Limits shape.
It captures 3 rate-limit definitions, measuring concurrent_requests, query_window_days, and requests_per_second.
Limit state is signalled in the published, rate_limit_headers, retry_after, and note response headers.
Tagged areas include Company, Advertising, AdTech, Mobile, and Retargeting.
publishedrate_limit_headersretry_afternote
Limits
Work with this as data
Every rate limit here is available over the APIs.io API and to AI agents over MCP.