LinkedIN CAPI Rate Limits

Sometimes clients reach out to us with a request to inspect why their LinkedIn CAPI has ceased tracking and results in an error code 429 or something like :

{ "status": 429, "serviceErrorCode": 101, "code": "TOO_MANY_REQUESTS", "message": "Resource level throttle APPLICATION_AND_MEMBER DAY limit for calls to this resource is reached." }

This error code does not result from a configuration within JENTIS.

Reason for this error: LinkedIn API Rate Limits

The usual reason for this is that the client has reached their rate limit for the LinkedIn CAPI. LinkedIn as a tracking tool applies a rate limit for the amount of requests it can process at a given time frame and ceases to process any requests once this limit is reached.

Quoted from LinkedIn´s support page: https://learn.microsoft.com/en-us/linkedin/shared/api-guide/concepts/rate-limits

“Rate limits specify the maximum number of API calls that can be made in a 24 hour period. These limits reset at midnight UTC every day.

There are two kinds of limits that affect your application:

• Application — The total number of calls that your application can make in a day.

• Member — The total number of calls that a single member per application can make in a day.

Your application's daily rate limit varies based on which API endpoint you are using. Standard rate limits are not published in documentation. You can look up the rate limit of any endpoint your app has access to through the Developer Portal. Select your app from the list and navigate to its Analytics tab. This page will only show usage and rate limits for endpoints you have made at least 1 request to today(UTC). If you want to look up a rate limit for an endpoint not listed in your app's Analytics page, make 1 test call to that endpoint and refresh the Analytics page. “

Solution suggestion:

From JENTIS, the suggestion is to try and split or distribute the tracking you are doing via the LI CAPI into as many possible apps as you can. Sometimes clients use one LI app to track multiple domains, country regions or elements , which leads to the quicker overload of the API requests. You can set up your LI app to be split across different country regions and create multiple instances of it, which would then help you distribute the data load and thus avoid reaching your rate limits too quickly.

We advise that you contact LinkedIn API support for further instructions on how to best apply this.

If you have any questions or feedback, please open a request on our Helpdesk.