Stay organized with collections
Save and categorize content based on your preferences.
Rate limiting connection traffic
This page describes how Integration Connectors rate limits (controls) the incoming requests to your connection,
and the various options available to you to address the rate limit conditions that may occur in your connection.
Integration Connectors intelligently manages a connection's traffic by
throttling (smoothening traffic spikes) requests from a connection. So, suppose
there is an increase in a connection's traffic; Integration Connectors automatically increases the number of
nodes assigned to the connection, and conversely, if there is a drop in a connection's
traffic, Integration Connectors automatically decreases the number of nodes assigned to the connection.
This node autoscaling ensures that a connection's node allocation is always optimal.
However, in some scenarios, it is possible that a connection uses all its available nodes
and still requires additional nodes. In such a scenario, where a connection exceeds
its throttling limits, Integration Connectors returns the HTTP 429 response.
Your options for rate limiting a connection vary based on your user type (pay-as-you-go or subscription)
as described in the following sections.
Rate limiting for pay-as-you-go users
Scenario
Remediation
Are you anticipating or seeing a spike in your connection's traffic?
Yes
Integration Connectors autoscales the connection nodes till it reaches the configured maximum node limit.
However, based on your traffic pattern, you can proactively configure the required minimum and
maximum nodes for the connection in the Edit connection page.
No
No action required from you.
Are you getting the HTTP 429 response for your connection?
Yes
Even though the connection nodes are autoscaled, you may have encountered the following scenarios:
There is a sudden spike in the connection's traffic which the existing nodes can't handle,
and hence you are temporarily getting this error. In this case, increase the number of minimum nodes for the connection in the Edit connection page.
The maximum permissible node limit isn't fully utilized by the connection. In this case, increase
the maximum nodes in the Edit connection page.
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Hard to understand","hardToUnderstand","thumb-down"],["Incorrect information or sample code","incorrectInformationOrSampleCode","thumb-down"],["Missing the information/samples I need","missingTheInformationSamplesINeed","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2025-08-26 UTC."],[[["\u003cp\u003eIntegration Connectors manages connection traffic by automatically adjusting the number of nodes assigned to a connection, increasing nodes during traffic spikes and decreasing them during lulls.\u003c/p\u003e\n"],["\u003cp\u003eIf a connection exceeds its throttling limits and uses all available nodes, Integration Connectors will return an \u003ccode\u003eHTTP 429\u003c/code\u003e response.\u003c/p\u003e\n"],["\u003cp\u003ePay-as-you-go users can proactively configure minimum and maximum node limits to handle anticipated traffic spikes, and must adjust node allocation, or contact support, when receiving \u003ccode\u003eHTTP 429\u003c/code\u003e errors.\u003c/p\u003e\n"],["\u003cp\u003eSubscription users have no actions to take when traffic spikes occur, as they are handled automatically, however, if they receive the \u003ccode\u003eHTTP 429\u003c/code\u003e response they must contact support.\u003c/p\u003e\n"]]],[],null,["# Rate limiting connection traffic\n================================\n\nThis page describes how Integration Connectors rate limits (controls) the incoming requests to your connection,\nand the various options available to you to address the rate limit conditions that may occur in your connection.\n\nIntegration Connectors intelligently manages a connection's traffic by\nthrottling (smoothening traffic spikes) requests from a connection. So, suppose\nthere is an increase in a connection's traffic; Integration Connectors automatically increases the number of\nnodes assigned to the connection, and conversely, if there is a drop in a connection's\ntraffic, Integration Connectors automatically decreases the number of nodes assigned to the connection.\nThis node autoscaling ensures that a connection's node allocation is always optimal.\n\nHowever, in some scenarios, it is possible that a connection uses all its available nodes\nand still requires additional nodes. In such a scenario, where a connection exceeds\nits throttling limits, Integration Connectors returns the `HTTP 429` response.\n\nYour options for rate limiting a connection vary based on your user type (pay-as-you-go or subscription)\nas described in the following sections.\n\nRate limiting for pay-as-you-go users\n-------------------------------------\n\nRate limiting for subscription users\n------------------------------------"]]
