Should I use Bulk API 2.0 or Bulk API 1.0?

Bulk API 2.0 for most loads: it splits your file into batches itself, so you upload one CSV per job. Bulk API 1.0 still suits jobs that need you to control batch sizes or use PK chunking on large queries.

How long are Bulk API results kept?

Seven days. Download the results of an ingest or query job within a week of it finishing, and within the retrieval timeout for each query result file.

Why did my Bulk API 2.0 job fail after many retries?

Bulk API 2.0 retries batches itself. A message that it retried too many times means the upload is too large or the query too broad: send a smaller file, or add filters to the query.

How do I see how many Bulk API query jobs are left today?

Call the REST limits resource. It reports the daily Bulk API 2.0 query jobs and the query result storage with their maximum and remaining values.

Salesforce Bulk API limits: 2.0 and 1.0

SalesforceBulk API 2.0 (and Bulk API 1.0)Bulk API and Bulk API 2.0 calls count toward the org's total API request allocation (see the salesforce row).

Daily or monthly allowance: 15,000 batches per rolling 24 hours, shared between Bulk API and Bulk API 2.0. In Bulk API 2.0 only ingest jobs consume batches, and batches are created automatically. Records uploaded per rolling 24 hours: 150,000,000 for both (Bulk API 1.0 is 15,000 batches x 10,000 records). Bulk API 2.0 query jobs: 10,000 per rolling 24 hours, with 1 TB of query results per rolling 24 hours.
Bulk and batch: Bulk API 2.0 ingest: up to 150 MB of base64-encoded CSV per job (upload no more than 100 MB to allow for encoding). Bulk API 1.0: up to 10,000 records, 10 MB and 10,000,000 characters per batch. Both versions: 5,000 fields and 400,000 characters per record, 131,072 characters per field. A job can stay open up to 24 hours (Bulk API 2.0: ingest jobs only). Results can be retrieved for 7 days. Queries: maximum retrieved file size 1 GB, 20 minutes to retrieve results. Bulk API 1.0 queries return at most 15 files; with PK chunking, chunks are 100,000 to 250,000 records. A Bulk API 1.0 query has a 2-minute processing limit.
Plans with API access: Same as the Salesforce API (Enterprise, Performance, Unlimited, Developer; Professional with the API add-on).
When you hit the limit: Bulk API 1.0 queries: more than 30 attempts returns 'Tried more than thirty times'; a query taking more than 2 minutes returns QUERY_TIMEOUT. Bulk API 2.0 retries automatically: for ingest, a message that it retried more than 20 times means use a smaller upload file; for queries, more than 15 retries means add filter criteria.
Limit headers: The /vXX.X/limits/ REST resource reports DailyBulkV2QueryJobs and DailyBulkV2QueryFileStorageMB.

Source: developer.salesforce.com (opens in a new tab), developer.salesforce.com: salesforce app limits platform api (opens in a new tab)

AttioREST API v2100 requests per second for reads and 25 per second for writes, across the whole API. Each record a write creates through a record reference counts as one more write. List records and List entries also have score-based limits: a per-query limit, and a summed limit over a 10-second sliding window shared by all apps and tokens.

Daily or monthly allowance: Not published
Bulk and batch: Not published
Plans with API access: Not published
When you hit the limit: HTTP 429 with type rate_limit_error and code rate_limit_exceeded, always with a Retry-After header giving the date when the limit resets (usually the next second).
Limit headers: Not published

Source: docs.attio.com (opens in a new tab)

ClarifyClarify API3,000 requests per minute, per workspace, per endpoint (rolling 60 seconds)

Daily or monthly allowance: Not published
Bulk and batch: Bulk endpoints take an array of records; no fixed cap per request (bounded by request body size); one bulk request counts as one request
Plans with API access: Not published
When you hit the limit: 429 Too Many Requests until the window resets, with Retry-After
Limit headers: X-RateLimit-Limit, X-RateLimit-Remaining, X-RateLimit-Reset, Retry-After

Source: developer.clarify.ai (opens in a new tab), developer.clarify.ai: bulk operations (opens in a new tab)

CloseREST API v1Limits are enforced per endpoint group (groups of URL paths and methods). Each API key has a lower limit, and the organization-wide limit is 3 times the per-key limit. The page gives no fixed numbers; 20 requests per second per key appears only as an example.

Daily or monthly allowance: Not published
Bulk and batch: Bulk actions (email, edit, delete, subscribe) act on all leads matching a search query or smart view. The page states no maximum number of records per action.
Plans with API access: Not published
When you hit the limit: HTTP 429 Too Many Requests, always with the RateLimit header and a Retry-After header. Pause for the rate_reset value (recommended over Retry-After) before calling that endpoint again. Some endpoints have stricter, unpredictable limits.
Limit headers: RateLimit (limit, remaining, reset). It replaces the old x-rate-limit-limit, x-rate-limit-remaining and x-rate-limit-reset headers.

Source: developer.close.com (opens in a new tab), developer.close.com: bulk actions (opens in a new tab)

CopperDeveloper API v1180 requests per minute for all API calls, over a rolling window. Bulk APIs have an additional limit of 3 requests per second.

Daily or monthly allowance: Not published
Bulk and batch: Bulk create and bulk update endpoints (people, leads, companies, opportunities, activities) accept at most 10 records per request; a larger request returns 422.
Plans with API access: Trial, Professional and Business plans
When you hit the limit: HTTP 429
Limit headers: Not published

Source: developer.copper.com (opens in a new tab), developer.copper.com: bulk create people (opens in a new tab), support.copper.com: 8823462 api docs and tips (opens in a new tab)

HubSpotHubSpot API (all public APIs; general limits)Public OAuth apps distributed through the HubSpot Marketplace: 110 requests per 10 seconds for each account that installs the app. This limit excludes the CRM Search API, and the API Limit Increase add-on does not raise it. Private (privately distributed) apps, counted per app: Free and Starter 100 requests per 10 seconds; Professional 190 per 10 seconds; Enterprise 190 per 10 seconds; any tier with the API Limit Increase add-on 250 per 10 seconds. CRM Search API: 5 requests per second per account.

Daily or monthly allowance: Private apps share one daily limit per account: Free and Starter 250,000 requests per day; Professional 625,000; Enterprise 1,000,000. Each API Limit Increase adds 1,000,000 per day on top of the base subscription, with a maximum of two increases. The daily limit resets at midnight in the account's time zone. The page gives no daily figure for public OAuth apps.
Bulk and batch: Batch endpoints: 100 records per request (for example, batch update contacts). CRM search: up to 200 records per page and 10,000 results per query; a query body can hold up to 3,000 characters, with up to 5 filterGroups of up to 6 filters each and 18 filters in total. Custom event completions batch endpoint: batches of 500.
Plans with API access: Every tier. The private-app rate-limit table lists Free, Starter, Professional and Enterprise (any Hub).
When you hit the limit: HTTP 429 on every call after the limit is exceeded. The JSON body includes status, message, errorType RATE_LIMIT, correlationId, policyName (DAILY or SECONDLY) and requestId. Error responses should stay under 5% of total daily requests, which Marketplace certification requires.
Limit headers: X-HubSpot-RateLimit-Daily, X-HubSpot-RateLimit-Daily-Remaining, X-HubSpot-RateLimit-Interval-Milliseconds, X-HubSpot-RateLimit-Max, X-HubSpot-RateLimit-Remaining (the two Daily headers are not sent on OAuth-authorized requests. X-HubSpot-RateLimit-Secondly and X-HubSpot-RateLimit-Secondly-Remaining are deprecated. Search endpoints send none of these headers.)

Source: developers.hubspot.com (opens in a new tab), developers.hubspot.com: search the crm (opens in a new tab), developers.hubspot.com: contacts guide (opens in a new tab)

InsightlyREST API v3.110 requests per second per instance

Daily or monthly allowance: Per instance, over a rolling 24 hours: Free/Gratis 1,000; Legacy plans 20,000; Plus 40,000; Professional 60,000; Enterprise 100,000.
Bulk and batch: The page lists no bulk endpoint. List responses return 100 records by default and up to 500 (top/skip paging).
Plans with API access: All plans
When you hit the limit: HTTP 429. After the daily threshold, requests to that endpoint are refused until the next day.
Limit headers: X-RateLimit-Limit, X-RateLimit-Remaining

Source: api.na1.insightly.com (opens in a new tab), support.insight.ly: CRM Plan Level Limits (opens in a new tab)

KeapKeap REST API (v1/v2)OAuth2 bearer tokens: 1,500 queries per minute per key/secret pair, across all Keap apps it accesses. Personal access tokens and service account keys: 10 queries per second and 240 per minute. Every consumer also has a per-second spike limit of 25 calls per second, which no header reports. Tenant throttle: 500 calls per minute (the header example shows a limit of 500 per minute, set by Keap).

Daily or monthly allowance: OAuth2 bearer tokens: 150,000 queries per day. Personal access tokens and service account keys: 30,000 queries per day. Both reset at 00:00 UTC.
Bulk and batch: Not published
Plans with API access: Not published
When you hit the limit: Not published
Limit headers: x-keap-product-quota-limit, x-keap-product-quota-time-unit, x-keap-product-quota-interval, x-keap-product-quota-available, x-keap-product-quota-used, x-keap-product-quota-expiry-time, x-keap-product-throttle-limit, x-keap-product-throttle-time-unit, x-keap-product-throttle-interval, x-keap-product-throttle-available, x-keap-product-throttle-used, x-keap-tenant-id, x-keap-tenant-throttle-limit, x-keap-tenant-throttle-time-unit, x-keap-tenant-throttle-interval, x-keap-tenant-throttle-available, x-keap-tenant-throttle-used

Source: developer.keap.com (opens in a new tab)

Microsoft Dynamics 365Dataverse Web API / SDK for .NET (service protection limits)Defaults per user, per web server: 6,000 requests within a 5-minute sliding window; 20 minutes (1,200 seconds) of combined execution time within the 5-minute window; 52 or more concurrent requests. Each web server enforces these limits on its own; trial environments have only one web server.

Daily or monthly allowance: Power Platform request limits per 24 hours: 40,000 per paid license (Power Platform paid users and Dynamics 365 except Team Member); 6,000 for Power Apps pay-as-you-go, Power Apps per app, Microsoft 365 apps with Power Platform access and Dynamics 365 Team Member. Non-licensed users with Dynamics 365 Enterprise and Professional share a pooled tenant limit of 500,000 base requests + 5,000 per USL, up to 10,000,000. Each Power Platform requests add-on adds 50,000 per 24 hours.
Bulk and batch: A batch can hold up to 1,000 operations (ExecuteMultipleRequest typically up to 1,000). Batching does not get around entitlement limits.
Plans with API access: Not published
When you hit the limit: Web API: HTTP 429 Too Many Requests with a Retry-After header in seconds. Error codes: 0x80072322 (number of requests), 0x80072321 (execution time), 0x80072326 (concurrent requests).
Limit headers: x-ms-ratelimit-burst-remaining-xrm-requests, x-ms-ratelimit-time-remaining-xrm-requests (for debugging only)

Source: learn.microsoft.com (opens in a new tab), learn.microsoft.com: api request limits allocations (opens in a new tab)

monday.comGraphQL API (platform API)Requests per minute: Enterprise 5,000, Pro 2,500, Other 1,000. Complexity: 5,000,000 points per query. App tokens: reads and writes each limited to 5M points per minute. Personal API tokens: 10M points per minute for reads and writes combined (1M for trial, NGO and free accounts). Concurrent requests: Enterprise 250, Pro 100, Other 40. Per IP address: 5,000 requests per 10 seconds. Some endpoints have lower limits, such as create board at 40 mutations per minute.

Daily or monthly allowance: Calls per day, reset at midnight UTC: Free 200, Standard/Basic 1,000, Pro/Trial 10,000, Enterprise 25,000. An API add-on raises it. Calls from marketplace apps and apps built by monday.com do not count.
Bulk and batch: Items query: 100 items
Plans with API access: All plans. The API is described as a free feature across all plans.
When you hit the limit: HTTP 429 with a Retry-After header; every rate-limit error also returns a retry_in_seconds field. Error codes include Rate Limit Exceeded, maxConcurrencyExceeded, COMPLEXITY_BUDGET_EXHAUSTED and IP_RATE_LIMIT_EXCEEDED (all 429). REQUEST_MAX_COMPLEXITY_EXCEEDED for one query over 5M. DAILY_LIMIT_EXCEEDED for the daily limit (no status code stated). A request that hits a rate limit still counts as 0.1 call toward the daily limit.
Limit headers: RateLimit-Policy, RateLimit (IETF structured fields; policies minuteRate, concurrency, complexityMinute)

Source: developer.monday.com (opens in a new tab), developer.monday.com: errors (opens in a new tab)

PipedriveREST API (v1 and v2)Burst limits per user token over a rolling 2-second window. With an API token: Lite 20, Growth 40, Premium 100, Ultimate 120 requests per 2 seconds. With OAuth apps: Lite 80, Growth 160, Premium 400, Ultimate 480 requests per 2 seconds. Search API: 10 requests per 2 seconds on every plan and authentication type.

Daily or monthly allowance: Daily token budget per company account, shared by all users: 30,000 base tokens x plan multiplier x number of seats, plus purchased API Token top-ups. Multipliers: Lite 1, Growth 2, Premium 5, Ultimate 7. Each endpoint costs tokens (for example get single entity 2, get list 20, update 10, search 40); v2 endpoints cost fewer. The budget resets at midnight in the server's time zone.
Bulk and batch: Not published
Plans with API access: The limit tables cover the Lite, Growth, Premium and Ultimate plans, for traffic with API tokens or OAuth tokens.
When you hit the limit: HTTP 429 Too Many Requests, and once the daily budget is used up, requests stay blocked until it resets. If an integration keeps sending high-volume api_token traffic after 429 responses, it can also get HTTP 403: a Cloudflare HTML error page.
Limit headers: x-ratelimit-limit, x-ratelimit-remaining, x-ratelimit-reset, x-daily-requests-left (POST/PUT requests left today in UTC; api_token requests only)

Source: pipedrive.readme.io (opens in a new tab)

SalesforceSalesforce Platform API (REST and SOAP; org-wide allocations)Concurrent long-running requests (20 seconds or longer): 5 for Developer Edition and Trial orgs, 25 for production orgs and sandboxes. Requests shorter than 20 seconds have no concurrency limit. REST and SOAP calls time out after 10 minutes; query calls follow the SOQL limits instead.

Daily or monthly allowance: Total API requests per 24-hour period, counted for the whole org rather than per user. Developer Edition: 15,000. Enterprise Edition, and Professional Edition with API access enabled: 100,000 plus licenses x calls per license (Salesforce 1,000; Salesforce Platform 1,000; Lightning Platform - One App 200), plus purchased API Call Add-Ons. Unlimited and Performance Edition: 100,000 plus licenses x calls per license (Salesforce 5,000; Salesforce Platform 5,000), plus add-ons. Full Sandbox: 5,000,000. Example: an Enterprise org with 15 Salesforce licenses gets 115,000. Calls that include DebuggingHeader have their own allocation of 1,000 per 24 hours. Paid orgs in active status may go over the limit by some amount, up to a hard cap; this does not apply to trial orgs, Developer Edition or sandboxes.
Bulk and batch: Bulk API and Bulk API 2.0 calls count toward this allocation. See the salesforce-rest and salesforce-bulk rows.
Plans with API access: On by default in Enterprise, Performance, Unlimited and Developer Edition. Professional Edition can add API access as an add-on. Each user also needs the API Enabled permission.
When you hit the limit: Too many concurrent long-running requests: REQUEST_LIMIT_EXCEEDED exception code. Daily limit exceeded (REST): HTTP 403 with error code REQUEST_LIMIT_EXCEEDED. Org without API access: API_DISABLED_FOR_ORG. Call over the time limit: REQUEST_RUNNING_TOO_LONG (SOAP) or QUERY_TIMEOUT (REST).
Limit headers: Sforce-Limit-Info (api-usage=used/limit) on REST responses. Other ways to check usage: the REST /services/data/vXX.X/limits resource (Max and Remaining, accurate within five minutes); Setup > System Overview (API Usage section and 'API Requests, Last 24 Hours'); the 30-day 'API Request Limit per Month' entitlement on the Company Information page; API Usage Notifications.

Source: developer.salesforce.com (opens in a new tab), developer.salesforce.com: intro rest compatible editions (opens in a new tab), developer.salesforce.com: headers api usage (opens in a new tab), developer.salesforce.com: errorcodes (opens in a new tab), developer.salesforce.com: resources limits (opens in a new tab)

SalesforceREST APIUses the org-wide daily allocation and the concurrent long-running request limits in the salesforce row. A Composite, sObject Collections, sObject Tree or Composite Graph request counts as one call toward API limits. In a Composite Batch request, each subrequest counts against rate limits.

Daily or monthly allowance: Shared with the org-wide allocation (see the salesforce row).
Bulk and batch: SOQL query: up to 2,000 records returned at a time. The Sforce-Query-Options batchSize is 2,000 by default, 200 minimum and 2,000 maximum, and the requested size is not guaranteed. Composite: up to 25 subrequests, of which up to 5 can be sObject Collections or query operations. Composite Batch: up to 25 subrequests. Composite Graph: up to 500 nodes and 75 graphs per payload, maximum graph depth 15. sObject Collections create, update, upsert and delete: up to 200 records per request (up to 10 chunks when object types are mixed). sObject Tree: up to 200 records across all trees, up to five record types, up to five levels deep.
Plans with API access: On by default in Enterprise, Performance, Unlimited and Developer Edition. Professional Edition needs the API add-on.
When you hit the limit: HTTP 403 with REQUEST_LIMIT_EXCEEDED when the org's API request limit is exceeded. Request size: the combined URI and headers may be up to 16,384 bytes per REST call; a longer URI returns 414 URI Too Long, and longer URI plus headers returns 431 Request Header Fields Too Large.
Limit headers: Sforce-Limit-Info

SugarCRMSugar REST API (SugarCloud-hosted instances)SugarCloud instances are expected to stay at or below 20 requests per second. Above that, or with inefficient requests, SugarCRM may block traffic. For sustained or planned traffic above 20 requests per second, file a case at least 7 calendar days ahead to agree on limits. SELECT queries are terminated after 120 seconds.

Daily or monthly allowance: Not published
Bulk and batch: Not published
Plans with API access: Not published
When you hit the limit: The offending IP addresses are temporarily blocked from Sugar's cloud, and a support case is opened. The page gives no HTTP status code.
Limit headers: Not published

Source: support.sugarcrm.com (opens in a new tab), support.sugarai.com: sugar cloud policy guide (opens in a new tab)

Zoho CRMREST API v8No time-based limit; requests are limited by concurrency per org per app: Free 5, Standard/Starter 10, Professional 15, Enterprise/Zoho One 20, Ultimate/CRM Plus 25. All editions also have a sub-concurrency limit of 10 for heavy APIs: Get Records with cvid or sort_by, Convert Lead, Insert/Update/Upsert of more than 10 records, Send Mail, Search records called from a function, Query API and Composite API. Bulk Read downloads: 10 requests per minute.

Daily or monthly allowance: API credits per rolling 24 hours, by edition. Free: 5,000. Standard/Starter: 50,000 + 250 per user license + add-on credits, up to 100,000. Professional: 50,000 + 500 per user license + add-ons, up to 3,000,000. Enterprise/Zoho One: 50,000 + 1,000 per user license + add-ons, up to 5,000,000. Ultimate/CRM Plus: 50,000 + 2,000 per user license + add-ons, unlimited maximum. Most calls cost 1 credit; some cost more (for example Convert Lead 5, Bulk Write 500 per job, Bulk Read 50). Trial editions get the same limits as the matching paid edition.
Bulk and batch: Insert/Update/Upsert: up to 100 records per call (1 credit per 10 records). Add/Remove Tags: up to 500 records per call. Bulk Write: up to 25,000 records and 200 column headers per CSV file, one CSV per zip, up to 25 MB, 500 credits per job. Bulk Read: up to 200,000 records per export job (ICS export up to 20,000 per call).
Plans with API access: All editions, including Free (5,000 credits).
When you hit the limit: HTTP 429 TOO_MANY_REQUESTS when the 24-hour credit limit or the concurrency limit is exceeded. Bulk Read over 10 downloads per minute also returns HTTP 429. More than 100 records in one insert returns LIMIT_EXCEEDED (HTTP 400).
Limit headers: X-API-CREDITS-REMAINING (sent once usage reaches 50% of the daily available credits)

Source: zoho.com (opens in a new tab), zoho.com: status codes (opens in a new tab), zoho.com: insert records (opens in a new tab), zoho.com: bulk write overview (opens in a new tab), zoho.com: limitations (opens in a new tab), zoho.com: limitations (opens in a new tab)

GongGong API3 API calls per second

Daily or monthly allowance: 10,000 API calls per day
Bulk and batch: Not published
Plans with API access: Available to all partners and customers; features available depend on the company's plan and assigned seats
When you hit the limit: HTTP 429; Retry-After gives the seconds to wait
Limit headers: Retry-After

Source: help.gong.io (opens in a new tab)

MixmaxREST API120 requests per minute per user, across all endpoints and tokens. Some endpoints have lower limits; for example, downloading call recordings allows 20 per minute. The limits are fixed and cannot be increased.

Daily or monthly allowance: Not published
Bulk and batch: Not published
Plans with API access: Mixmax Pro, Meeting Copilot, Inbox Copilot, Engagement Copilot, Mixmax Suite, Mixmax for Teams
When you hit the limit: HTTP 429 with a Retry-After header giving the seconds to wait
Limit headers: X-RateLimit-Limit, X-RateLimit-Remaining, X-RateLimit-Reset (Unix seconds)

Source: developer.mixmax.com (opens in a new tab), success.mixmax.com: 11643056 mixmax rest api (opens in a new tab)

OutreachREST API v210,000 requests per hour per user; some endpoints, such as the Bulk API and Kaia, have their own rules. Kaia recordings and transcripts: 3 API calls per second per org.

Daily or monthly allowance: Kaia recordings and transcripts: 6,000 API calls per day per org. Bulk actions: 5 million records per day, a limit shared with the Outreach client. The allowance refills gradually through the day.
Bulk and batch: A bulk request can cover at most 100,000 items; a larger one does not start and is marked failed. Bulk upsert requests are limited to 2 MB. Page size must not be larger than 1000. Offset paging stops at an offset of 10,000.
Plans with API access: Not published
When you hit the limit: HTTP 429 with a JSON error (id rateLimitExceeded). Bulk requests over the daily item limit also get 429. Fetching an access token more than once every 60 seconds may also return 429.
Limit headers: X-RateLimit-Limit, X-RateLimit-Remaining, X-RateLimit-Reset (aliased as Retry-After)

Source: developers.outreach.io (opens in a new tab), developers.outreach.io: bulk api (opens in a new tab), developers.outreach.io: making requests (opens in a new tab)

ReplyAPI v3Per user: 100 requests per minute and 3,000 per hour. All apps, scripts and services acting for the same user share the count. Reporting (/v3/reporting/*), sequence statistics and support endpoints have lower limits. Each API limit package adds the standard limits once more (2 packages = 300 per minute, 9,000 per hour, 450,000 per week).

Daily or monthly allowance: 150,000 requests per week per user, over a rolling 7 days
Bulk and batch: Not published
Plans with API access: Not published
When you hit the limit: HTTP 429 Too Many Requests with Retry-After in seconds and an application/problem+json body. 429 responses carry no x-rate-limit headers.
Limit headers: x-rate-limit-limit (the period, such as 1h or 7d), x-rate-limit-remaining, x-rate-limit-reset (only on successful responses; they report the longest-period limit). GET /v3/rate-limits returns every limit with usage.

Source: docs.reply.io (opens in a new tab)

SalesBlinkSalesBlink APILimits depend on request type: GET requests 30 per minute, POST and PATCH 15 per minute, PUT and DELETE 10 per minute. Contact SalesBlink for higher limits.

Daily or monthly allowance: Not published
Bulk and batch: Not published
Plans with API access: Not published
When you hit the limit: Not published
Limit headers: Not published

Source: developer.salesblink.io (opens in a new tab)

SalesloftSalesloft API (v2)600 cost per minute per team, shared by every integration on that team. Most endpoints cost 1. Requests for page numbers above 100 cost more: pages 101-150 cost 3 points, 151-250 cost 8, 251-500 cost 10, 501 and above cost 30.

Daily or monthly allowance: Not published
Bulk and batch: Bulk jobs: up to 5,000 records per job-data upload call, with no limit on uploads per job. One bulk job runs at a time per tenant. Once a job starts running, no further rate limits apply to it. Paged endpoints: per_page from 1 to 100 (default usually 25).
Plans with API access: Not published
When you hit the limit: Not published
Limit headers: x-ratelimit-endpoint-cost, x-ratelimit-remaining-minute

Source: developers.salesloft.com (opens in a new tab), developers.salesloft.com: filtering paging sorting (opens in a new tab), developers.salesloft.com: intro (opens in a new tab), developers.salesloft.com: bulk jobs job data create (opens in a new tab)

UnifyData API v1100,000 requests per five-minute window

Daily or monthly allowance: Not published
Bulk and batch: Not published
Plans with API access: Not published
When you hit the limit: Not published
Limit headers: Not published

Source: docs.unifygtm.com (opens in a new tab)

ActiveCampaignAPI v35 requests per second per account. Bulk Contact Importer: 20 requests per minute for single-contact requests, 100 requests per minute for multi-contact requests.

Daily or monthly allowance: Not published
Bulk and batch: Bulk contact import: up to 250 contacts per request (a request with more is rejected with 400), with a payload under 400K bytes (399,999 bytes or less). The import runs asynchronously and returns a batchId.
Plans with API access: Not published
When you hit the limit: HTTP 429 Too Many Requests with a Retry-After header in seconds
Limit headers: RateLimit-Limit, RateLimit-Remaining (Retry-After on 429)

Source: developers.activecampaign.com (opens in a new tab), developers.activecampaign.com: bulk import contacts (opens in a new tab)

BrazeREST APISet per endpoint. /users/track: 3,000 requests per 3 seconds for customers whose pricing has data points (otherwise per contract). /messages/send broadcast calls: 250 per minute, and 10 per minute per unique audience. /users/delete, /users/identify, /users/merge and the alias endpoints share 20,000 per minute. /users/export/ids: 250 per minute (onboarded on or after Aug 22, 2024) or 2,500 per minute (before that)

Daily or monthly allowance: 250,000 requests per hour shared across a listed group of endpoints, including campaign, Canvas and message sends to individual recipients. Limits reset on the clock hour
Bulk and batch: /users/track: up to 75 objects combined across attributes, events and purchases per request
Plans with API access: Not published
When you hit the limit: HTTP 429. Wait the seconds in X-RateLimit-Retry-After if present, otherwise until X-RateLimit-Reset
Limit headers: X-RateLimit-Limit, X-RateLimit-Remaining, X-RateLimit-Reset, X-RateLimit-Retry-After

Source: braze.com (opens in a new tab)

BrevoBrevo API v3Depends on endpoint and tier. General tier (all plans): 100 requests per hour for most endpoints, 10 per second for /v3/contacts, 1,000 per second for POST /v3/smtp/email. Advanced tier (Professional, Enterprise): 200 requests per hour for most endpoints, 20 per second for contacts, 2,000 per second for email send. Extended tier (Enterprise): 600 requests per hour for most endpoints, 60 per second for contacts, 6,000 per second for email send

Daily or monthly allowance: Hourly caps (RPH) per endpoint, e.g. 3,600,000 per hour for POST /v3/smtp/email and 36,000 per hour for /v3/contacts on the General tier
Bulk and batch: Not published
Plans with API access: All plans (Free, Starter, Standard, Professional, Enterprise) get the General tier
When you hit the limit: HTTP 429 Too Many Requests with the rate-limit headers. Read the reset header to know how long to wait
Limit headers: x-sib-ratelimit-limit, x-sib-ratelimit-remaining, x-sib-ratelimit-reset

Source: developers.brevo.com (opens in a new tab), developers.brevo.com: limit headers (opens in a new tab)

Customer.ioTrack API and App APITrack API: no fixed limit; guideline about 3,000 requests per 3 seconds (about 1,000 per second). App API: 10 requests per second for most endpoints, 1 request every 10 seconds for API-triggered broadcasts, no limit on transactional messages

Daily or monthly allowance: Not published
Bulk and batch: Track API v2 /batch: requests up to 500kb, each request in the batch up to 32kb
Plans with API access: Not published
When you hit the limit: Track API: requests are not rejected or dropped for volume. App API: not documented
Limit headers: Not published

Source: docs.customer.io (opens in a new tab), docs.customer.io: app (opens in a new tab)

KlaviyoKlaviyo APIPer account and per endpoint, in tiers from XS (1 per second burst, 15 per minute steady) to XL (350 per second burst, 3,500 per minute steady). OAuth apps get their own quota for each account they are installed in

Daily or monthly allowance: Not published
Bulk and batch: Bulk profile import: up to 10,000 profiles per request, 5MB payload (endpoint limit 10 per second burst, 150 per minute steady)
Plans with API access: Not published
When you hit the limit: HTTP 429 with a Retry-After header (seconds). The RateLimit headers are not sent on a 429
Limit headers: RateLimit-Limit, RateLimit-Remaining, RateLimit-Reset

Source: developers.klaviyo.com (opens in a new tab), developers.klaviyo.com: bulk import profiles (opens in a new tab)

LoopsLoops API v110 requests per second per team. Content API (campaigns, components, email messages, themes, transactional emails, uploads, workflows): 60 requests per 60 seconds per team

Daily or monthly allowance: Not published
Bulk and batch: Not published
Plans with API access: Not published
When you hit the limit: HTTP 429 Too Many Requests. Retry with exponential backoff
Limit headers: x-ratelimit-limit, x-ratelimit-remaining

Source: loops.so (opens in a new tab)

MailchimpMarketing API10 simultaneous connections per user (not per API key or client)

Daily or monthly allowance: Not published
Bulk and batch: Batch endpoint: at most 500 pending batch webhook events per user. Batch subscribe or unsubscribe: up to 500 members per call
Plans with API access: Not published
When you hit the limit: HTTP 429. At very high volumes, a 429 or 403 with no JSON body
Limit headers: Not published

Source: mailchimp.com (opens in a new tab), mailchimp.com: batch subscribe or unsubscribe (opens in a new tab)

OmnisendOmnisend API400 requests per minute per brand by default (sliding window). Stricter limits on some endpoints, e.g. /segments POST/PUT 15 per minute, /contacts/tags 60 per minute

Daily or monthly allowance: /analytics/reports and /analytics/statistics: 55 requests per 24 hours (plus 10 per minute)
Bulk and batch: Batches endpoint: up to 100 actions per batch operation, for products, contacts, events and categories
Plans with API access: Not published
When you hit the limit: HTTP 429 Too Many Requests. Some endpoints include a retryAfter field (seconds) in the error body
Limit headers: Not published

Source: api-docs.omnisend.com (opens in a new tab), api-docs.omnisend.com: post batches (opens in a new tab)

OrttoOrtto API (the current docs call the product Ortto; Autopilot help articles are hosted in the Ortto Knowledge Base)Per plan: Sandbox 5, Starter 10, Professional 30, Enterprise 30 requests per second. Per IP: 2,000 requests per 10 seconds and 6,000 per 60 seconds. Enterprise can ask for more

Daily or monthly allowance: Not published
Bulk and batch: Up to 100 contacts, or 100 activities, per payload. 2MB per payload
Plans with API access: Not published
When you hit the limit: HTTP 429 with a JSON body that includes try-in-seconds
Limit headers: Not published

Source: help.ortto.com (opens in a new tab), help.ortto.com: a 490 autopilot rate limit segment destination (opens in a new tab)

Twilio SendGridWeb API v3A fixed number of requests per refresh period, set per endpoint. The numbers are not published; the X-RateLimit headers on each response report them

Daily or monthly allowance: Not published
Bulk and batch: Mail Send: at most 1,000 recipients per request and under 30MB total including attachments. Add or update contacts: up to 30,000 contacts or 6MB per request, whichever is lower
Plans with API access: Not published
When you hit the limit: HTTP 429 Too Many Requests. The endpoint stays blocked for the rest of the refresh period
Limit headers: X-RateLimit-Limit, X-RateLimit-Remaining, X-RateLimit-Reset

Source: twilio.com (opens in a new tab), twilio.com: mail send (opens in a new tab), twilio.com: add or update a contact (opens in a new tab)

ChurnZeroREST API (OData v4)Per instance, per minute: 1 to 100 requests run normally, 101 to 200 are delayed, more than 200 get 429

Daily or monthly allowance: Not published
Bulk and batch: Up to 100 filter expressions per request; grouped ($apply) results capped at 100 groups
Plans with API access: Not published
When you hit the limit: 429 Too Many Requests above the hard max (200 requests per minute); requests between the soft and hard max are progressively delayed
Limit headers: Not published

Source: app.churnzero.net (opens in a new tab)

FreshdeskAPI v2Per account, per minute: Growth 100, Pro 400, Enterprise 700. Trials 50. Sub-limits, e.g. ticket create 50/160/280 and tickets list 40/100/200 per minute (Growth/Pro/Enterprise). More can be bought (1,000 or 2,000 per minute)

Daily or monthly allowance: Not published
Bulk and batch: Not published
Plans with API access: Not published
When you hit the limit: HTTP 429 with Retry-After (seconds). Invalid requests count toward the limit
Limit headers: X-RateLimit-Total, X-RateLimit-Remaining, X-RateLimit-Used-CurrentRequest, Retry-After, X-RateLimit-Account-Total, X-RateLimit-Account-Used, X-RateLimit-Account-Remaining, X-RateLimit-Sublimit-Total, X-RateLimit-Sublimit-Used, X-RateLimit-Sublimit-Remaining

Source: developers.freshdesk.com (opens in a new tab)

FrontCore APIPer company: Starter 50, Professional 100, Enterprise 200 requests per minute. Extra limits on heavy routes, e.g. analytics 1 request per 3 seconds, search 40% of your rate limit. Raising the limit beyond the default requires Professional or higher

Daily or monthly allowance: Not published
Bulk and batch: Not published
Plans with API access: Not published
When you hit the limit: HTTP 429 Too Many Requests with retry-after (seconds)
Limit headers: x-ratelimit-limit, x-ratelimit-remaining, x-ratelimit-reset, retry-after, x-front-tier

Source: dev.frontapp.com (opens in a new tab)

GladlyGladly REST API10 requests per second per method (GET, POST, PUT, PATCH, DELETE) per organization. Reports API: POST 10 per minute, 2 concurrent requests across the organization

Daily or monthly allowance: Not published
Bulk and batch: Not published
Plans with API access: Tokens belong to users with the API User permission
When you hit the limit: HTTP 429. Retry with exponential backoff
Limit headers: Ratelimit-Limit-Second, Ratelimit-Remaining-Second

Source: developer.gladly.com (opens in a new tab), help.gladly.com: default api rate limits (opens in a new tab)

GorgiasREST APILeaky bucket. API key: 40 requests per 20 seconds. OAuth2 apps: 80 requests per 20 seconds. Enterprise accounts: same counts over a 10-second window

Daily or monthly allowance: Not published
Bulk and batch: Not published
Plans with API access: Not published
When you hit the limit: HTTP 429 Too Many Requests with Retry-after (seconds)
Limit headers: Retry-after, X-Gorgias-Account-Api-Call-Limit

Source: developers.gorgias.com (opens in a new tab)

Help ScoutInbox API 2.0Per account: Standard up to 200, Plus up to 400, Pro up to 800 calls per minute. Writes (POST, PUT, DELETE, PATCH) and Search Conversations count as 2 requests

Daily or monthly allowance: Not published
Bulk and batch: Not published
Plans with API access: Standard, Plus and Pro. Standard has no reporting endpoints. The Free plan has no API access
When you hit the limit: HTTP 429. X-RateLimit-Retry-After gives the seconds to wait
Limit headers: X-RateLimit-Limit-Minute, X-RateLimit-Remaining-Minute, X-RateLimit-Retry-After

Source: developer.helpscout.com (opens in a new tab), docs.helpscout.com: 1140 mailbox api (opens in a new tab)

IntercomREST APIPrivate apps: 10,000 calls per minute per workspace, shared by all private apps. Public apps: 10,000 calls per minute per app. Both: 25,000 calls per minute per workspace across all apps. Enforced in 10-second windows (per-minute limit divided by 6)

Daily or monthly allowance: Not published
Bulk and batch: Not published
Plans with API access: Not published
When you hit the limit: HTTP 429 Too Many Requests with error code rate_limit_exceeded. Not every 429 has the rate-limit headers
Limit headers: X-RateLimit-Limit, X-RateLimit-Remaining, X-RateLimit-Reset

Source: developers.intercom.com (opens in a new tab)

LINEMessaging APIPer channel and per endpoint (token bucket). 2,000 requests per second for most endpoints. Send multicast: 200 per second. Narrowcast, broadcast and statistics endpoints: 60 per hour. Audience endpoints: 60 per minute

Daily or monthly allowance: Monthly message quota (free plus additional messages) set by pricing plan. Going over it returns 429 'You have reached your monthly limit.'
Bulk and batch: Multicast: up to 500 user IDs and 5 messages per request. Up to 10 concurrent audience upload operations per audience
Plans with API access: Not published
When you hit the limit: HTTP 429 Too Many Requests
Limit headers: Not published

Source: developers.line.biz (opens in a new tab)

LiveChatText platform APIs (Agent Chat API v3.5, Configuration API)Not published

Daily or monthly allowance: Monthly API call quota: Essential 10,000, Growth 20,000, Enterprise custom. Extra 100,000-call packages can be bought
Bulk and batch: Not published
Plans with API access: Not published
When you hit the limit: too_many_requests ('Too many requests') error. The block lifts automatically after some time
Limit headers: Not published

Source: platform.text.com (opens in a new tab), livechat.com: pricing (opens in a new tab)

PlainGraphQL APIPer workspace, API key traffic only: Launch & Foundation 450, Grow & Horizon 600, Scale & Frontier 1,000 requests per minute

Daily or monthly allowance: Not published
Bulk and batch: Not published
Plans with API access: Not published
When you hit the limit: HTTP 429 with error code RATE_LIMITED. Work out the retry time from x-ratelimit-reset
Limit headers: x-ratelimit-limit, x-ratelimit-remaining, x-ratelimit-reset

Source: help.plain.com (opens in a new tab)

TidioTidio OpenAPIPer project: Plus 60 requests per minute, Premium 120 per minute. Free Trial, Starter, Growth and paid Lyro AI Agent / Flows: 10 per minute, product recommendation endpoints only

Daily or monthly allowance: Not published
Bulk and batch: Create multiple contacts: up to 100 contacts per request
Plans with API access: Plus and Premium get the full API. Free Trial, Starter, Growth and Lyro AI Agent / Flows get product recommendation endpoints only. Not available on Free
When you hit the limit: HTTP 429 with error code too_many_requests
Limit headers: x-ratelimit-limit, x-ratelimit-remaining

Source: developers.tidio.com (opens in a new tab), developers.tidio.com: post contacts batch (opens in a new tab)

ZendeskSupport APIPer minute, by Suite plan: Team 200, Growth 400, Professional 400, Enterprise 700, Enterprise Plus 2,500. High Volume API add-on: 2,500. Per-endpoint caps too, e.g. Incremental Exports 10 per minute (30 with High Volume)

Daily or monthly allowance: Not published
Bulk and batch: Create Many / Update Many Tickets: up to 100 tickets per request. Up to 30 queued or running jobs at once
Plans with API access: Not published
When you hit the limit: HTTP 429 Too Many Requests with Retry-After (seconds). Over the job limit you get a TooManyJobs error
Limit headers: X-Rate-Limit, X-Rate-Limit-Remaining, ratelimit-limit, ratelimit-remaining, ratelimit-reset, zendesk-ratelimit-tickets-index, zendesk-ratelimit-inflight-jobs

Source: developer.zendesk.com (opens in a new tab), developer.zendesk.com: tickets (opens in a new tab)

Zoho DeskZoho Desk APIConcurrency per portal: Free/Trial 5, Express 10, Standard 10, Professional 15, Enterprise/Zoho One/CRM Plus 25 simultaneous calls. No per-minute cap while you stay within concurrency

Daily or monthly allowance: Credits per 24 hours: Free/Trial 5,000; Express 25,000 + 100 per user; Standard 50,000 + 250 per user; Professional 75,000 + 500 per user; Enterprise/Zoho One/CRM Plus 100,000 + 1,000 per user. Paid editions can buy up to 5,000,000. A simple fetch costs 1 credit; list calls cost 3 to 100 credits depending on record range
Bulk and batch: All APIs return at most 50 records per request. Bulk updates cost 1 credit per 2 records
Plans with API access: Not published
When you hit the limit: Daily credits used up: HTTP 429 with Retry-After. Concurrency exceeded: TOO_MANY_REQUESTS error
Limit headers: X-Rate-Limit-Request-Weight-v3, X-Rate-Limit-Remaining-v3, Retry-After

Source: desk.zoho.com (opens in a new tab)

AmplitudeHTTP V2 API (event ingestion)30 events per second per user_id or device_id (rolling 30-second average); 50,000 events per second per project across the HTTP API and HTTP V2 endpoints. Free plan: no more than 100 requests per second and 1,000 events per second, with no more than 10 events per request

Daily or monthly allowance: Batch Event Upload API: 500,000 events per user or device per rolling 24 hours (enforced after Amplitude determines that a user or device is spamming)
Bulk and batch: HTTP V2: up to 2,000 events per request, body under 1 MB. Batch Event Upload API: 2,000 events per batch, 20 MB payload, 1,000 events per second per device or user. Dashboard REST API: 5 concurrent requests per API key; up to 108,000 query cost per hour; User Activity and User Search share 10 concurrent and 360 queries per hour per project
Plans with API access: Not published
When you hit the limit: 429 Too Many Requests (body includes eps_threshold and throttled devices/users); pause that user or device 30 seconds, or wait 60 seconds if the project limit is hit. 413 if a request is too large. Dashboard REST API: 429, honor Retry-After if present
Limit headers: Not published

Source: amplitude.com (opens in a new tab), amplitude.com: batch event upload (opens in a new tab), amplitude.com: dashboard rest (opens in a new tab)

BranchDeep Linking API (plus Query, Aggregate and export APIs)Deep Linking API: POST 200 per second / 12,000 per minute / 300,000 per hour; GET 100 per second / 5,500 per minute / 100,000 per hour; PUT 100 per second / 1,000 per minute / 10,000 per hour. Query API: 5 per second, 20 per minute, 150 per hour. Aggregate, Cohort, Cross-Events Export: 2 per second, 5 per minute, 150 per hour. Custom Exports: create 10 per minute and 25 per hour

Daily or monthly allowance: Not published
Bulk and batch: POST /v1/url/bulk/{branch_key} creates links in bulk, 100 KB payload limit
Plans with API access: Availability varies by Branch plan
When you hit the limit: 429 'Rate limit reached.' (Query API body: 'Limit is exceeded for org....')
Limit headers: Not published

Source: help.branch.io (opens in a new tab), help.branch.io: query overview (opens in a new tab), help.branch.io: aggregate overview (opens in a new tab), help.branch.io: custom exports overview (opens in a new tab), help.branch.io: app (opens in a new tab)

FullstoryServer API (v2)Per-second and burst limits exist but no numbers are published

Daily or monthly allowance: Server events are capped by a per-account quota per monthly or annual cycle (amount shown in account settings)
Bulk and batch: Batch user and batch event import: up to 50,000 objects per request; 100 in-progress batches per org (more are queued); 429 once there are 200 in-progress batches or 500,000 individual operations
Plans with API access: Not published
When you hit the limit: 429 with a Retry-After header giving the seconds to wait. Requests over the server event quota also get 429
Limit headers: Retry-After

Source: developer.fullstory.com (opens in a new tab), developer.fullstory.com: getting started (opens in a new tab), developer.fullstory.com: create batch user import job (opens in a new tab), developer.fullstory.com: create batch events import job (opens in a new tab)

GainsightGainsight CS REST APISynchronous calls: 100 per minute (fixed window); recommended limits, may vary by package

Daily or monthly allowance: Synchronous calls: 100,000 per day. Bulk (asynchronous) API: 10 calls per hour and 100 per day
Bulk and batch: REST calls insert or update up to 50 records per call; use the Bulk API for more
Plans with API access: Limits can vary based on your package
When you hit the limit: Not published
Limit headers: Not published

Source: support.gainsight.com (opens in a new tab), support.gainsight.com: Gainsight CS System Limits (opens in a new tab)

Google AnalyticsGoogle Analytics Data API (GA4) v1Core tokens per property per hour: 40,000 (Standard), 400,000 (Analytics 360). Core tokens per project per property per hour: 14,000 (Standard), 140,000 (360). Concurrent requests per property: 10 (Standard), 50 (360). Server errors per project per property per hour: 10 (Standard), 50 (360). 120 potentially thresholded requests per property per hour

Daily or monthly allowance: Core tokens per property per day: 200,000 (Standard), 2,000,000 (Analytics 360); daily quotas refresh at midnight Pacific Standard Time
Bulk and batch: batchRunReports / batchRunPivotReports: up to 5 reports per call (each report still counts toward quota)
Plans with API access: Not published
When you hit the limit: 429 RESOURCE_EXHAUSTED once any quota bucket reaches 0; retry with truncated exponential backoff. Remaining quota is returned in the response body with returnPropertyQuota: true
Limit headers: Not published

Source: developers.google.com (opens in a new tab)

MixpanelIngestion (Import) API, Query API, Raw Data Export APIIngestion: 2 GB of uncompressed JSON per minute or about 30,000 events per second per project (rolling 1 minute). Query API: 5 concurrent queries and 60 queries per hour. Raw Data Export API: 100 concurrent queries, 60 queries per hour, 3 queries per second. Lexicon Schemas API: 5 requests per minute. /flags: 500 requests per minute per IP

Daily or monthly allowance: Not published
Bulk and batch: Import API: up to 2,000 events and 10 MB uncompressed per request; each event under 1 MB
Plans with API access: Not published
When you hit the limit: 429 (Import: 'Project exceeded rate limits. Please retry the request with exponential backoff.'); 413 if the payload is too large. No Retry-After documented
Limit headers: Not published

Source: docs.mixpanel.com (opens in a new tab), docs.mixpanel.com: import events (opens in a new tab)

PendoEngage API (v1)Not published

Daily or monthly allowance: Not published
Bulk and batch: Bulk delete: up to 500 visitors or accounts per request. Segment upload: up to 10 million visitor or account IDs. Aggregations: 5-minute runtime or 4 GB of output. Metadata bulk update: any number of records, but the call is limited to 5 minutes (408 on timeout)
Plans with API access: Depends on your level of service with Pendo; requires an integration key from your subscription
When you hit the limit: 429 Too Many Requests: 'Too many requests hit the API too quickly. Slow down.'
Limit headers: Not published

Source: engageapi.pendo.io (opens in a new tab), support.pendo.io: 8174659206043 Error Pendo API timeout (opens in a new tab)

PostHogREST API (private endpoints, personal API key)Analytics endpoints: 240 per minute and 1,200 per hour. events/values: 60 per minute and 300 per hour. Query endpoint: 2,400 per hour. Other CRUD endpoints: 480 per minute and 4,800 per hour. Feature flag local evaluation: 600 per minute. Counted per personal API key. Public capture endpoints are not rate limited

Daily or monthly allowance: Invites only: 50 per hour and 200 per day
Bulk and batch: /batch capture route: no limit on events per batch, request body under 20 MB by default. /invites/bulk: up to 20 invites per request
Plans with API access: The API is available for all users and instances
When you hit the limit: Not published
Limit headers: Not published

Source: posthog.com (opens in a new tab), posthog.com: capture (opens in a new tab)

VitallyREST API1,000 requests per minute (token bucket); write requests may count as more than one request

Daily or monthly allowance: Not published
Bulk and batch: List endpoints return up to 100 items per page
Plans with API access: Not published
When you hit the limit: 429 Too Many Requests
Limit headers: RateLimit-Limit, RateLimit-Remaining, RateLimit-Reset

Source: docs.vitally.io (opens in a new tab)

Google AdsGoogle Ads APIQPS limits apply per customer ID and per Google Cloud project, but no fixed number is published (varies with server load). Planning Service: 1 QPS. Keyword Plan Idea methods: 1 request per second per customer ID

Daily or monthly allowance: Test access: 15,000 operations per day (test accounts only). Explorer: 2,880 operations per day against production accounts. Basic: 15,000 operations per day. Standard: unlimited
Bulk and batch: Up to 10,000 mutate operations per request. Conversion uploads: 2,000 per request. Offline user data jobs: up to 100,000 user identifiers across operations, recommended max 1,000,000 operations per job
Plans with API access: Access level of the Google Cloud project: Test (granted on enabling the API, test accounts only), Explorer, Basic (requires brand verification), Standard
When you hit the limit: Rate limit: RESOURCE_TEMPORARILY_EXHAUSTED; retry with exponential backoff and jitter. Daily operations: RESOURCE_EXHAUSTED. Too many mutates: TOO_MANY_MUTATE_OPERATIONS
Limit headers: Not published

Source: developers.google.com (opens in a new tab), developers.google.com: rate limits (opens in a new tab), developers.google.com: access levels (opens in a new tab)

MetaMarketing APIAd account scoring: max score 60 (development tier, blocked 300 seconds) or 9,000 (full access, blocked 60 seconds); read = 1 point, write = 3 points. Mutation endpoints: 100 requests per second per app and ad account. One edit per object every 30 seconds

Daily or monthly allowance: Hourly per-ad-account business use case limits: ads_management = (100,000 full access or 300 dev tier) + 40 x active ads; ads_insights = (190,000 full access or 600 dev tier) + 400 x active ads - 0.001 x user errors; custom_audience between 190,000 (full) or 5,000 (dev) and 700,000. Spending limit changes: 10 per day; ad set budget changes: 4 per hour
Bulk and batch: Not published
Plans with API access: Limited tier by default when you add the Marketing API product; Full access through App Review gives more quota
When you hit the limit: Error codes 17 (User request limit reached), 613 (too many calls from this ad account), 80000/80003/80004/80014 (too many calls from this ad account), 4 (Application request limit reached)
Limit headers: X-Ad-Account-Usage, X-Business-Use-Case, X-FB-Ads-Insights-Throttle

Source: developers.facebook.com (opens in a new tab)

BigQueryBigQuery API100 API requests per second per user per method; 300 concurrent API requests per user; jobs.get and tabledata.list: 1,000 requests per second per project; projects.list: 10 per second per user

Daily or monthly allowance: On-demand query usage: 200 TiB per project per day (adjustable); 1,500 load jobs per table per day
Bulk and batch: Streaming inserts: up to 50,000 rows per request (500 recommended), 10 MB HTTP request; 1 GB per second per project in US/EU multi-regions, 300 MB per second elsewhere. Storage Write API: 3 GB per second in multi-regions, 300 MB per second in regions. tabledata.list returns up to 100,000 rows
Plans with API access: Not published
When you hit the limit: HTTP 403 with reason rateLimitExceeded (short-term, retry with exponential backoff), quotaExceeded, or apiLimitExceeded
Limit headers: Not published

Source: docs.cloud.google.com (opens in a new tab), docs.cloud.google.com: troubleshoot quotas (opens in a new tab)

DatabricksREST API (workspace and account)Set per endpoint and per workspace. Examples: Jobs API runs/get 100 per second, runs/submit 35 per second, jobs/create 20 per second; DBFS 30 per second; Permissions GET 100 per second; Pipelines GET 150 per second; Secrets API 1,100 per minute; Workspace export 60 per second; Account SCIM GET 20 per second; MLflow tracking 120 per second (search 7 per second)

Daily or monthly allowance: Data lineage: table lineage 300 per hour and 1,200 per day; column lineage 1,500 per hour and 6,000 per day (per account)
Bulk and batch: Not published
Plans with API access: Not published
When you hit the limit: HTTP 429 Too Many Requests; retry with exponential backoff and jitter, and wait at least Retry-After if present
Limit headers: Retry-After

Source: docs.databricks.com (opens in a new tab), docs.databricks.com: rest api (opens in a new tab)

AirtableWeb API5 requests per second per base; 50 requests per second for all traffic from one user's or service account's personal access tokens

Daily or monthly allowance: Monthly calls per workspace: Free 1,000; Team 100,000 (then slowed to 2 requests per second until the month resets); Business and Enterprise Scale no monthly cap
Bulk and batch: Not published
Plans with API access: All plans; Free and Team have monthly call caps
When you hit the limit: 429; wait 30 seconds before requests succeed again. Free plan over the monthly cap: one-time 30-day grace period, then calls are blocked until the month resets
Limit headers: Not published

Source: airtable.com (opens in a new tab), support.airtable.com: managing api call limits in airtable (opens in a new tab)

CalendlyAPI v2Per user: paid plans 500 requests per minute, Free 50 per minute. Create Event Invitee on paid non-Enterprise plans: 10 per minute and 50 per hour; on Enterprise: 500 per minute. Up to 8 OAuth tokens per user per minute

Daily or monthly allowance: Create Event Invitee: 5 requests per user per day on Free and Trial, 100 per user per day on paid non-Enterprise plans
Bulk and batch: Not published
Plans with API access: All plans, including Free. A few endpoints (activity log, deleting invitee or event data) are Enterprise-only
When you hit the limit: HTTP 429 Too Many Requests
Limit headers: X-RateLimit-Limit, X-RateLimit-Remaining, X-RateLimit-Reset

Source: developer.calendly.com (opens in a new tab), calendly.com: calendly api overview (opens in a new tab)

Google SheetsGoogle Sheets API v4Read requests: 300 per minute per project, 60 per minute per user per project. Write requests: 300 per minute per project, 60 per minute per user per project

Daily or monthly allowance: No daily limit while you stay within the per-minute quotas
Bulk and batch: Each batch request, including its subrequests, counts as one request. Recommended max payload 2 MB; requests time out after 180 seconds
Plans with API access: All standard use is available at no additional cost
When you hit the limit: 429: Too many requests; retry with truncated exponential backoff (quota refills each minute)
Limit headers: Not published

Source: developers.google.com (opens in a new tab)

ProductboardPublic REST API50 requests per second per access token (default)

Daily or monthly allowance: Not published
Bulk and batch: Not published
Plans with API access: Pro plan or higher
When you hit the limit: HTTP 429 Too Many Requests with Retry-After (seconds)
Limit headers: X-RateLimit-Limit, X-RateLimit-Remaining, Retry-After

Source: developer.productboard.com (opens in a new tab), developer.productboard.com: getting started (opens in a new tab)

TypeformCreate API and Responses API2 requests per second per Typeform account (Create and Responses APIs). Webhooks and Embed have no rate limit

Daily or monthly allowance: Not published
Bulk and batch: Not published
Plans with API access: Standard Typeform accounts. No separate developer account needed
When you hit the limit: Not published
Limit headers: Not published

Source: typeform.com (opens in a new tab)

Adobe CommerceREST and GraphQL web APIs (order and payment-information rate limiting, 2.4.7 and later)No default limit: optional rate limiting for placing orders and payment information is disabled by default. When enabled, the merchant sets a request limit per guest (IP address) and per signed-in customer over 60, 3,600 or 86,400 seconds; the timeout is three times that period

Daily or monthly allowance: Not published
Bulk and batch: Asynchronous bulk REST endpoints; on Commerce as a Cloud Service the limit comes from the Maximum Entities per Bulk Request store setting
Plans with API access: Not published
When you hit the limit: REST: 429 Too Many Requests. GraphQL: HTTP 200 OK, with a Too Many Requests error in the response body
Limit headers: Not published

Source: developer.adobe.com (opens in a new tab), developer.adobe.com: bulk endpoints (opens in a new tab)

BigCommerceREST API (OAuth apps)Per-store quota refreshed every 30 seconds and shared by all apps on the store: Growth & Core 150 per 30 seconds (20k per hour); Scale 450 per 30 seconds (60k per hour); Performance set by plan and resource; Unlimited Rate Plan (some Performance clients) has no request rate limits

Daily or monthly allowance: Not published
Bulk and batch: Batch product update: max 10 products per request
Plans with API access: Not published
When you hit the limit: 429 Too Many Requests; wait the X-Rate-Limit-Time-Reset-Ms value (milliseconds) before retrying
Limit headers: X-Rate-Limit-Time-Window-Ms, X-Rate-Limit-Time-Reset-Ms, X-Rate-Limit-Requests-Quota, X-Rate-Limit-Requests-Left

Source: docs.bigcommerce.com (opens in a new tab), docs.bigcommerce.com: update products (opens in a new tab)

ShopifyAdmin API (GraphQL Admin API and legacy REST Admin API)GraphQL Admin: calculated query cost per app per store, with restore rate Standard 100 points/second, Advanced Shopify 200, Shopify Plus 1,000, enterprise (Commerce Components) 2,000; a single query can cost at most 1,000 points. REST Admin (legacy): Standard 2 requests/second, Advanced Shopify 4, Shopify Plus 20, enterprise (Commerce Components) 40; default bucket of 40 requests per app per store (400 on Shopify Plus)

Daily or monthly allowance: Once a store has 500,000 product variants, at most 10,000 new variants per day on any API (does not apply to Shopify Plus)
Bulk and batch: Bulk operations have no max cost or rate limits; on API 2026-01 and later, up to five bulk queries and five bulk mutations per app per shop at once (earlier versions: one of each type); bulk queries must finish within 10 days, bulk mutations within 24 hours; input arrays max 250 items
Plans with API access: Not published
When you hit the limit: REST: 429 Too Many Requests with a Retry-After header in seconds. GraphQL: throttle error when the bucket fills; the daily variant throttle returns 429
Limit headers: X-Shopify-Shop-Api-Call-Limit, Retry-After (REST); GraphQL reports extensions.cost.throttleStatus (maximumAvailable, currentlyAvailable, restoreRate) in the response body

Source: shopify.dev (opens in a new tab), shopify.dev: rate limits (opens in a new tab), shopify.dev: usage limits (opens in a new tab), shopify.dev: queries (opens in a new tab), shopify.dev: imports (opens in a new tab)

ChargebeeREST API v2Live sites, per minute by plan: Starter 150, Performance 1,000, Enterprise (default) 3,500, Enterprise (custom) no upper limit; test sites 150 per minute. Concurrency limit: 50 GET and 100 POST requests at once

Daily or monthly allowance: Not published
Bulk and batch: Not published
Plans with API access: Not published
When you hit the limit: 429 (api_request_limit_exceeded), may include a Retry-After header; concurrent updates to the same resource can return 429 lock_timeout
Limit headers: Retry-After

Source: apidocs.chargebee.com (opens in a new tab)

PaddlePaddle Billing API240 requests per minute per IP address for most operations; 1,000 requests per minute per IP address for pricing preview endpoints (preview transaction and preview prices)

Daily or monthly allowance: Per subscription: up to 20 chargeable (immediate-charge) updates per hour, with a maximum of 100 per 24 hours
Bulk and batch: Not published
Plans with API access: Not published
When you hit the limit: 429 too_many_requests with a Retry-After header; the IP address can't make another request for 60 seconds
Limit headers: Retry-After

Source: developer.paddle.com (opens in a new tab)

PlaidPlaid APIPer endpoint, per Item and per client, in fixed windows. Production examples: /accounts/get 15 per minute per Item and 15,000 per minute per client; /item/get 15 per minute per Item and 5,000 per minute per client; /auth/get and /identity/get 15 per minute per Item; /transactions/sync 50 per minute per Item and 2,500 per minute per client; /accounts/balance/get 5 per minute and 30 per hour per Item, 1,200 per minute per client. The published table is not exhaustive

Daily or monthly allowance: /transactions/refresh in Production: 100 per minute, 18,000 per hour and 432,000 per day per client. Limited Production has a free call allocation per product and an Item creation cap
Bulk and batch: Not published
Plans with API access: Not published
When you hit the limit: HTTP 429 with error_type RATE_LIMIT_EXCEEDED and an endpoint-specific error_code (e.g. ACCOUNTS_LIMIT)
Limit headers: Not published

Source: plaid.com (opens in a new tab)

RechargeRecharge APILeaky bucket per merchant (standard 1x1): bucket of 40 requests, leak rate of 2 requests per second

Daily or monthly allowance: Not published
Bulk and batch: Async batch endpoints are recommended for backend processes; the rate-limit page states no max size
Plans with API access: Not published
When you hit the limit: 429 Too Many Requests; Recharge advises sleeping at least 2 seconds before retrying
Limit headers: Not published

Source: docs.getrecharge.com (opens in a new tab)

StripeREST API (v1)100 requests per second per account in live mode, 25 per second in sandbox; most individual endpoints 25 requests per second; Search API 20 read requests per second; Files API 20 reads and 20 writes per second; Payouts create 15 per second; default live-mode concurrency limit of 50 in-progress requests

Daily or monthly allowance: Read (GET) requests must not exceed an average of 500 per transaction over a rolling 30 days, with a minimum of 10,000 read requests per month for every account; write requests have no allocation limit
Bulk and batch: Not published
Plans with API access: Not published
When you hit the limit: 429 Too Many Requests with a Stripe-Rate-Limited-Reason header (global-rate, endpoint-rate, global-concurrency, endpoint-concurrency, resource-specific)
Limit headers: Stripe-Rate-Limited-Reason

Source: docs.stripe.com (opens in a new tab)

Auth0Management API v2Free: 2 requests per second (burst 2). Enterprise: production tenants burst 50 and sustained 16 per second, non-production burst 10 and sustained 2 per second. Essentials and Professional: per-endpoint limits, e.g. Read Users 500 per minute (burst 40), all other endpoints combined 150 per minute (burst 10)

Daily or monthly allowance: Not published
Bulk and batch: User import jobs: 500KB file limit, two concurrent import jobs per tenant, jobs time out after 2 hours
Plans with API access: Not published
When you hit the limit: 429 Too Many Requests
Limit headers: x-ratelimit-limit, x-ratelimit-remaining, x-ratelimit-reset

Source: auth0.com (opens in a new tab), auth0.com: free public (opens in a new tab), auth0.com: enterprise public (opens in a new tab), auth0.com: essentials professional b2b (opens in a new tab), auth0.com: rate limit use cases (opens in a new tab), auth0.com: bulk user imports (opens in a new tab)

ClerkBackend APIPer application instance (Secret Key): production 1,000 requests per 10 seconds, development 100 per 10 seconds. Updates to a user, Organization or membership: 10 per 10 seconds per object. POST /v1/invitations 100 per hour; POST /v1/organizations/{organization_id}/invitations 250 per hour

Daily or monthly allowance: Not published
Bulk and batch: POST /v1/invitations/bulk: 25 requests per hour; POST /v1/organizations/{organization_id}/invitations/bulk: 50 requests per hour
Plans with API access: Not published
When you hit the limit: 429 with a Retry-After header giving the seconds until the block expires
Limit headers: Retry-After

Source: clerk.com (opens in a new tab)

G2G2 API v1 (data.g2.com)100 requests per second (global)

Daily or monthly allowance: Not published
Bulk and batch: Not published
Plans with API access: Requires an API token; endpoint access depends on account permissions (ask your G2 Account Executive)
When you hit the limit: 429 Too Many Requests; access blocked for 60 seconds
Limit headers: Not published

Source: data.g2.com (opens in a new tab)

LobLob API (v1)150 requests per 5 seconds per endpoint per API key (same for Test and Live keys); POST /v1/us_verifications and POST /v1/us_autocompletions 300 per 5 seconds; single-address US and international verification 300 calls per 5 seconds

Daily or monthly allowance: Not published
Bulk and batch: Bulk US verifications: 70 calls per 10 seconds, max 20 addresses per call. Bulk international verifications: 30 calls per 10 seconds, max 20 addresses per call
Plans with API access: Not published
When you hit the limit: 429 Too Many Requests, code rate_limit_exceeded, with a message to wait 5 seconds and retry
Limit headers: X-Rate-Limit-Limit, X-Rate-Limit-Remaining, X-Rate-Limit-Reset

Source: docs.lob.com (opens in a new tab), help.lob.com: av faqs (opens in a new tab)

WarmlyAgent Tools REST APINot published

Daily or monthly allowance: 250 credits a month with every Warmly account; the API meters credits, not request counts
Bulk and batch: Not published
Plans with API access: Every Warmly account; API keys are issued per organization from the Warmly admin UI
When you hit the limit: Not published
Limit headers: Not published

Source: warmly-knowledge-base.help.usepylon.com (opens in a new tab)

Salesforce Bulk API limits for 2.0 and 1.0

How to read the limits

How to size a bulk load

What to do next

Salesforce Bulk API limits: questions

Should I use Bulk API 2.0 or Bulk API 1.0?

How long are Bulk API results kept?

Why did my Bulk API 2.0 job fail after many retries?

How do I see how many Bulk API query jobs are left today?

Keep going