Connection limits
The rate, size and time limits on calls through a connection, and how long a consent link or an approval stays good.
These limits are there to protect the person's account and the platform. Design your app so a normal day stays well inside them.
How many calls
Calls are counted for each connection, each minute. Go over and the call answers 429 connection_rate_limited, with a retry-after header that says how many seconds are left in the minute.
google-workspacemicrosoft-graphgoogle-sheetsgoogle-driveslackGood to know The count belongs to the connection, not to the app. In
ownermode every visitor shares one connection, so they share one limit. Inusermode each person has their own connection and so their own limit.
Google and Microsoft also have limits of their own, which they set. If they answer with their own error, it comes back unchanged.
How big
Request body, google-workspaceRequest body, google-driveRequest body, microsoft-graphRequest body, google-sheetsRequest body, slackProvider answerPathQuery stringConnection nameA body that is too big answers 413 request_too_large. An answer that is too big answers 502 response_too_large. Ask for less: a smaller range, one page at a time.
How long
One call to the provider504 upstream_timeoutRedirects followedGET and HEAD onlySDK retries429, 502, 503, 504Consent linkStarting a connectAn approval, once approvedHow many permissions and files
Permissions on one grantFiles in restrict_toRenewing logins
A login is renewed by the platform a little before it runs out, once at a time, so a burst of calls does not cause a burst of renewals. Calls that arrive in the middle wait up to 5 seconds for it. If a provider says no for good, the connection becomes needs_reauth (reconnect).
See also: limits for the whole platform.