Quick Answer: Want to know api rate limits stripe shopify google merchant platforms typical values? Stripe for instance, charges based on “the number of requests per second” (100 in live mode vs 25 in a sanddox). Shopify employs a cost-based strategy with a 100–2,000 points per second based on plan. Google’s Merchant API never returns one number as quotas are auto adjusted based on methods. All three can be updated; see the official documentation before you build anything off of them.
Typical Values Compared
| Platform | Limit model | Typical value | Where to verify |
| Typical application | nLoRAFive | 10,000 base counts | 10,000 to 100,000 base counts / no smt/no 24″ rack mount components or drawers |
| Stripe | Requests Per Second | 100 live, 25 sandbox | Stripe rate-limits docs — |
| Shopify GraphQL Commerce (Admin) | An estimated number of points per second by plan, based on the number of calculated queries per page.Shopify GraphQL Admin | The number of calculated queries a page contains, between 100 and 2,000 points per second by plan. | |
| Google Analytics API | Fixed public quotas (cannot modify) | Unlimited, with exceptions as well | No public figure / Available on a per-user basis via the Quota.list method |
These limit models vary across the api rate limits stripe shopify google merchant platforms typical values, and for this reason, the ‘requests per minute’ number alone can’t describe all three.
Quick Overview
A quick overview of the api rate limits stripe shopify google merchant platforms typical values.
Stripe
Stripe’s core rate limiter is set to 100 ops per second in live and 25 ops per second in a sandbox. Requests can go from 25 requests per second to individual endpoints, unless stated otherwise, and limits may be increased for certain accounts depending on use by Stripe.
Tighter endpoint limits are in place:
- Files API: 20 ops/sec to read and 20 ops/sec to write file operations
- Search API: 20 ops/second of reading
- Payment Intents: Update up to 1,000 PaymentIntents per hour.
- Email you can use the following names for these services, plus a few exceptions: Subscription: 10 new invoices per subscription per minute ;
- Create Payout: 15 requests / second and 30 concurrent requests / business
- Connect: Up to 30 accounts per second in GO 10/Up to 50 accounts per second in GO 20/Up to 100 accounts per second in GO 30.
For metering the events in live mode, 1,000 calls per second per account is a different limit. Stripe also mentions in this post that read requests should not be exceeding an average of 500 per transaction and states that it’s not highly encouraged to load test in test mode as limits are lower and latency is different in test versus live environments.
As for the text: The older docs / third-party guides reference 100 read ops and 100 write ops; the newer are written as 100 ops. Look in the current page.
Shopify
Limits on Shopify’s GraphQL Admin API are determined by the number of tokens that matched the query, rather than how many requests were made. Limitations apply per combination of app and store; these limits are bucket size and restore rate per plan. These rates of restoration are listed on the current limits page:
| Plan | GraphQL Admin restore time |
| Standard | 100pps |
| lasses at cheapest prices! | |
| Plus Shopify | 1000x/sec |
| Shopify for enterprise | 2000 points per second |
There is no cap on the number of points per query, subject to plan. Limits will use the leaky bucket method, so it is OK to have peaks if the average cost is less than the restore rate. Bulk operations: For large reads and writes, the limits for per-query don’t apply to bulk operations. Attach Shopify-GraphQL-Cost-Debug: 1 to understand the cost contribution of each field.
It’s important to note that there are some guides around by third party sources who claim that the bucket is restored at 50 points per second, to take it back to 1,000 points. Those figures seem to be old data, trust shopify.dev.
Keep in mind that on Oct. 1, 2024, the REST Admin API was marked as a legacy API, and as of April 1, 2025, all new public apps that are submitted to the App Store will mandate GraphQL with no support for REST.
Google Merchant API
Google does not show a specific number. The Merchant API automatically adjusts quotas for the products and merchant accounts based on usage, by method. Anything more than that results in quota/request_rate_too_high for per-minute limits and quota/daily_limit_exceeded for the daily limits. Google recommends making an equal number of calls throughout the day. Check the limits and usage and request increases as needed using the Quota.list method.
Here too, migration is an issue. As reported in Google’s notice, Content API for Shopping will be retired on Aug. 18, 2026 and it will be replaced by Merchant API as mentioned by Google. That date is once more passed, ensure your migration status at the moment.
The Problem With Typical Values
Always consider any vote of a “typical value” as a starting point as:
- Limits are imposed on an account/per app. You can have your burst mixed in with other jobs in a bucket!
- Models differ. Stripe counts requests, Shopify counts costs and Google tracks them per method.
- Platforms change. Limits can be temporarily reduced by Shopify to ensure stability, and can be increased through Stripe on a per account basis.
Budget-Pace-Backoff Method (Original Framework)
- Budget. Know your own peak cps / cpm and leave some “headroom. With Shopify, guess values, rather than calls.
- Pace. Include a clientside limiter so to ensure your code always remains within the limit. Divide google calls all day rather than one late night “tennis” call.
- Backoff. For any request that is limited, repeat the request with exponential backoff and don’t flood the endpoint. Based on the actual restore rate from the reply, give a wait for Shopify.
Use bulk/batch processing tools like Shopify Bulk Tools when available on the platform in preference to numerous calls.
Rate Limiting Checklist (Linkable Asset)
- I have verified each limit on the platform’s official page now published.
- I can identify the model (Request, Cost point, or per-method quota)
- Peak load with headroom estimated
- Implemented client side pacing
- Used exponential backoff and retry with it
- I’m bulk operating or batching large jobs
- Logging limit errors and cost/quota information.
- I was looking at my ‘Plan Tier’ because they do alter Shopify limits
- Not load testing up to sandbox or test limits
Guest Post Angles
These topics are suitable for developer/ecommerce/integration magazines:
- Three ways APIs count your usage: requests, cost points and per-method quotas.
- Content API for Shopping to Merchant API: quota changes.
- Rates available for sync jobs: exploring sync rate-limit pacing and bulk patterns.
Do Less for More, Then Ask for More
Use the table above as a sketch for use when planning the api rate limits stripe shopify google merchant platforms typical values for a project, rather than relying on it as a contract. Have each number verified on the official page, program pacing and backoff into your code and ask for a greater limit when the actual usage has been measured.
One Response