faq

Our Person Profile Endpoint scrapes public LinkedIn profiles only. And if a user does not share their profile picture publicly, then the profile picture of their public LinkedIn profile would be a placeholder image. We cannot discern if an image is a placeholder picture or not because an image is

Proxycurl's Person Profile API Endpoint [https://nubela.co/proxycurl/linkedin] 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

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 (ten) posts. For company

The short answer is -- as stable as LinkedIn lets us be. 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

The customer support staff at Proxycurl can help you change your email address. However, it is not a direct change. What we can do is to transfer credits from one account to another. We are not able to help you move over 1. the credit cards added to the original

No, Proxycurl is not able to fetch connections of users for two reasons..

There are two reasons why it happens in our Person Profile API Endpoint [https://nubela.co/proxycurl/linkedin]: 1. The interpretation of first and last names might vary between people. For example, my name is "Steven Goh." Some people might consider "Steven" the first name, and others might consider it

Yes we do! You can use the Company Search Endpoint & Person Search Endpoint.

Proxycurl scrapes public Linkedin profiles in real-time and on-demand. Web scraping takes time, and on average. Every API Request dispatches a real-time job to scrape a profile. Because each API request is a job to scrape a profile live, it takes about 5-6 seconds to complete and the API to

When we scrape a public Linkedin profile for example with our Person Profile API [https://nubela.co/proxycurl/linkedin], we are served with a temporary CDN URL by Linkedin which usually begins with https://media-exp... Some of our customers store the temporary CDN URL which expires in an unpredictable manner.

LinkDB [https://nubela.co/proxycurl/linkdb] is updated with every real-time (API) request to scrape a Linkedin profile. Essentially, this methodology keeps data on LinkDB constantly updated to the count of (up to) millions of profiles a day.

Proxycurl is a pay-as-you-go service. Credits cost US$0.01 / credit. Credit cost varies with API endpoints. You can check out the API documentation [https://nubela.co/proxycurl/docs#enrichment-api] for the price (in credits) of various API endpoints. We offer volume pricing for our Enterprise plans You have to

Get 10,000 credits every month. Here is how.

We only scrape public profiles, and it turns out that Skills data is not a part of public profiles. We can only return what we can scrape, as such we do not scrape Skills data. However, we are working with external partners to help you enrich skills data via Person

Proxycurl only scrapes public LinkedIn profiles. Sometimes, the privacy settings of a profile keep certain portions of a private profile hidden publicly. We can only return what exists on the public profile. This is why the profile returned might be missing some data that is otherwise present on a private

Our API succeeds 90+% of the time. It turns out that our scraping infrastructure is limited and inconsistent because we are dealing with external targets such as LinkedIn which is very erratic when it comes to rate limits, particularly with their public profiles. We notice 503s occur more during the

Do you have a budget of $10 for testing the service? If so, are you able to head over to the dashboard and make a top-up? $10 will yield you 100 credits, which I believe should be plenty for you to evaluate the service. In our early days, we offered

Proxycurl only scrapes public Linkedin profiles. Some Linkedin profiles do not have public profiles (due to privacy settings [https://nubela.co/blog/the-ultimate-guide-to-linkedin-public-profile-visibility/]). And if the public profile does not exist, then we are not able to scrape it. This is when we return 404. You can verify that a

No, we are not able to resolve Sales Navigator URLs into regular profile URLs. As such, we are not able to scrape Sales Navigator URLs. The reason is that Sales Navigator links require an active Linkedin login session to resolve into profiles. And we do not scrape Linkedin profiles with