Workaround for Clay API Minimum Rate Limit with LinkedIn

·May 16, 2025 03:03 PM·

Hi, has anyone found a workaround for the minimum rate limit for API calls from Clay? I would like to use LinkedIn APIs which only have rate limits of 1 req / sec. Possibly do you know a queuing service or sth similar so that we can use the API within Clay?

1

3 comments

· Sorted by Oldest

Discuss Anything

Workaround for Clay API Minimum Rate Limit with LinkedIn

Alexander F.

·May 16, 2025 03:03 PM·

Hi, has anyone found a workaround for the minimum rate limit for API calls from Clay? I would like to use LinkedIn APIs which only have rate limits of 1 req / sec. Possibly do you know a queuing service or sth similar so that we can use the API within Clay?

1

3 comments

· Sorted by Oldest

kushagra t.
·
·
n8 workflow to call the api wait for response then push to clay, you can then lookup in the og table to get the data
Alexander F.
·
·
Thanks Kushagra! Good pointer
Alexander F.
·
·
I know that some APIs first have a kind of "waiting" status and update later (e.g. Instantly). Does the same logic also work with an API wrapper that continues to call the API and does anyone know of such a service that works out of the box?

kushagra t.
·
·
n8 workflow to call the api wait for response then push to clay, you can then lookup in the og table to get the data
Alexander F.
·
·
Thanks Kushagra! Good pointer
Alexander F.
·
·
I know that some APIs first have a kind of "waiting" status and update later (e.g. Instantly). Does the same logic also work with an API wrapper that continues to call the API and does anyone know of such a service that works out of the box?