Weave · Rate Limits

Weave Rate Limits

Weave does not publicly publish fixed numeric rate limits for its developer API (api.weaveconnect.com); the authoritative reference is gated behind a developer login in the Weave Developer Portal (dp.getweave.com). API access is scoped to a location subscription, and practical throughput is governed more by product-level allowances than by a documented per-second request cap. The most concrete published quota is on outbound bulk (mass) texting: the Messaging API exposes a bulk-message-quota endpoint, indicating that mass-text volume is metered per account/location. Telephony and SMS throughput are additionally bounded by underlying carrier and 10DLC messaging regulations. Numeric per-endpoint limits below are marked as not published and should be reconciled once portal access is available.

Weave Rate Limits is the machine-readable rate-limit profile for Weave on the APIs.io network, conforming to the API Commons Rate Limits specification.

It captures 4 rate-limit definitions, measuring requests, messages, and subscriptions.

The profile also includes 3 backoff/retry policies defined and response codes documented for throttled.

Tagged areas include Communication, Healthcare, Rate Limiting, and Quotas.

4 Limits Throttle: 429
CommunicationHealthcareRate LimitingQuotas

Limits

API Requests location
requests
not published
No fixed numeric per-second/per-minute request rate is documented publicly; reference is login-gated.
Bulk Message Quota account
messages
per plan (queryable)
Mass/bulk texting is metered; remaining quota is returned by GET /v1/account/bulk-message-quota.
SMS Throughput phone_number
messages
carrier / 10DLC bound
Outbound SMS is constrained by carrier and 10DLC campaign throughput rules, not solely by Weave.
Event Subscriptions location
subscriptions
not published
Subscription counts per client/location are not documented publicly.

Policies

Backoff Strategy
On HTTP 429, honor Retry-After and retry with exponential backoff plus jitter.
Bulk Messaging Governance
Check remaining bulk-message quota before sending mass texts, and respect opt-out/consent and 10DLC requirements.
Location Scoping
Requests are scoped to a single Weave location; distribute load across locations rather than exceeding a single location's allowances.

Sources

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/weave-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 email required.

GitHub Google LinkedIn

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