Steven Goh

For people profiles, our API offers the following: articles - Articles posted by the useractivities -  see https://nubela.co/proxycurl/docs#people-api-person-profile-endpoint-response-activityFor companies, our API follows the following: updates - See https://nubela.co/proxycurl/docs#company-api-company-profile-endpoint-response-companyupdateDo note that we are only able to pull the recent few posts

Proxycurl API returns profiles of varying levels freshness. Profiles that are less than 29 days old. Use use_cache=if-recent parameter to enable profile freshness of <= 29 days On average, 88% of profiles are fetched in real-time when this parameter is provided. The other 12% of profiles are popular

We scrape public LinkedIn profiles only. And if a user does not share his profile picture publicly, then the profile picture of the public LinkedIn profile would be a placeholder image. We cannot discern if an image is a placeholder picture or not because an image is an image. So

Let's start by looking at this snippet of an email from a customer looking to acquire LinkDB Snapshots from us: Hello Steven,I'm back to revisiting this (sorry for the delay). It's down to you and CoreSignal. CoreSignal has similar data. They're more expensive if we use US (about $130k

Proxycurl's Person Profile API Endpoint works with LinkedIn profiles of any country, as long as the profile is public. Public LinkedIn profiles can be viewed without being logged into LinkedIn. (See this article for the difference between a public LinkedIn profile VS a private LinkedIn profile)

More often or not, Proxycurl is not the bottleneck for your application. On a regular account, every account has a rate limit of 300 requests every minute. So, in theory, you can make 432,000 API requests per day, which amounts to $4320 per day at a minimum. This brings

Yes, we do for people profiles, with caveats. The articles and activities values in our Person Profile Endpoint describe a profile's post activities. However, given that we scrape public LinkedIn profiles, our API can only scrape what is present on the public profile: the most recent (three) posts. For company

The short answer is -- as stable as LinkedIn lets us. It is a constant cat-and-mouse game with LinkedIn. Given that we scrape public LinkedIn profiles only. There are quite a few moving parts that we have no control over, such as: If LinkedIn removes a particular data field from