Docs
OverviewPlatformPlatform APIA2P Messaging API
AI & MCP
Open dashboard
OverviewPlatformPlatform APIA2P Messaging API
AI & MCP
  • Overview
  • Introduction
  • Create an account
  • Choose your API
  • Authentication
  • AI & MCP
Product API
  • Guide
  • Quickstart
    • API tokens
    • Connected apps (OAuth)
    • Project readiness
    • Channel readiness
    • Senders
    • Attention
    • Recommendations
    • Overview
    • Contacts and attributes
    • Events
    • Query filter
    • Event query filter
    • Probes
    • Counting and retrieval
    • Segments
    • Overview
    • Creating a draft
    • Audience targeting
    • Message content
    • Dates and scheduling
    • Reading campaigns
    • Estimating and deleting
    • OverviewBeta
    • Templates
    • Creating and editing drafts
    • Triggers and exits
    • Nodes
    • Delays and waits
    • Overview
    • Statistics catalog
    • Building queries
    • Conversions & revenue
    • Reading results
    • Flow reports
    • Rate limits
    • Errors
  • Full API Reference
Ingest API
  • Guide
  • Quickstart
  • Authentication
  • Rate limits
  • Errors
  • Best practices
  • Full API Reference
Further reading
  • Query Filter
DashboardSupportinstasent.com

Platform API · Ingest API

Ingest API rate limits

Ingest traffic is rate-limited per datasource and per endpoint. Each response reports the current window through X-RateLimit headers, and breaching the limit returns 429.

On this page▾
  • Reading the headers
  • Batch, don't hammer
  • When you hit the limit
  • What's next

Every Ingest endpoint enforces a request-per-minute ceiling, scoped by datasource and by endpoint. Limits are sized to your subscription plan and documented per endpoint in the API Reference — if you need more throughput for a backfill or a traffic spike, open a ticket with the expected peak rate and we will raise the ceiling on your datasource.

Reading the headers

Every response includes three headers with the current window state. Log them in production — they are the cheapest way to spot a client that is about to hit the wall.

X-RateLimit-Limit      600
X-RateLimit-Remaining  597
X-RateLimit-Reset      1893452400
HeaderMeaning
X-RateLimit-LimitTotal requests allowed in the current window.
X-RateLimit-RemainingRequests left before the window tightens.
X-RateLimit-ResetUnix timestamp when the counter resets.

Batch, don't hammer

Both POST /stream/contacts and POST /stream/events accept up to 100 items per call. A single batched request counts as one hit against the rate limit, so batching is the cheapest way to move volume without tripping the ceiling. Drop to smaller batches only when your source system produces records one at a time.

When you hit the limit

Requests that exceed the window return 429 Too Many Requests. The body is empty; the X-RateLimit-Reset header tells you when to retry.

Back off exponentially rather than retrying in a tight loop. A client that hammers a 429 response keeps the window full and never recovers — waiting until X-RateLimit-Reset resolves the situation cleanly.

What's next

  • Errors — every status code you might receive, including 429.
  • API Reference — per-endpoint documentation.

Last updated September 30, 2026

PreviousAuthenticationNextErrors
  • Reading the headers
  • Batch, don't hammer
  • When you hit the limit
  • What's next

© 2026 Instasent

Privacy PolicyTerms & ConditionsCookie PolicyLegal Notice
All systems operational