Instagram Creator Marketplace Discovery rate limit: 5,000/hour

Meta's changelog says the account-level rate limit for the Creator Marketplace Discovery API is now 5,000 calls per user per hour, up from 1,000. Sume's POST /v1/influencer-search does not draw on that quota: Sume counts requests per API key per minute, with reads and writes in separate budgets.

Meta's number is from its Instagram Platform changelog; Sume's are from the authentication docs and OpenAPI document, read 2026-10-01.

What does Meta's new limit work out to?

5,000 calls in an hour averages about 83 calls a minute (5,000 divided by 60), against about 17 a minute at the old 1,000. The changelog gives only the hourly figure and says it applies at the account level per user; it does not describe per-minute pacing, so spread calls evenly instead of bursting.

What budget does a Sume shortlist call spend?

The authentication docs define a read as any GET or HEAD plus two non-submitting POSTs; everything else is a write. By that rule POST /v1/influencer-search spends the write budget, which the plan sets.

Do the two limits share a quota?

No. Meta's cap is enforced by Meta on your Meta account; Sume's budget is enforced on your Sume API key. A 429 from Sume names the exhausted budget in error.details.scope (read or write); see 429 scope read or write. Hitting one limit tells you nothing about the other.

How do I keep a Sume search small?

Set limit (1 to 24, default 12) to the shortlist you will actually review. The docs' natural-language example uses "limit": 8. Search results are documented as unbilled, so the cost of a loop is request budget, not credits. Read ratelimit-remaining and back off on retry-after instead of counting calls yourself.