faq

This post applies to the following API endpoints: Company Lookup EndpointRole Lookup EndpointPerson Lookup EndpointWork Email Lookup EndpointOccasionally, our Lookup API endpoints return the wrong results. False positives, to be precise. This happens because our Lookup Endpoints is a search function. Even Google gets search results wrong. There are two

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

The customer support staff at Nubela 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 the credit cards added to the original accountthe

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

There are two reasons why it happens. 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 last. So erroneous user input on Linkedin can result in inaccurate results.

Proxycurl does not have an API endpoint that mirrors the search functionality you get in Linkedin after signing in. The reason is that we only scrape public pages on Linkedin that do not require a user session. But, we do have search. Given that we provide developer tools as a

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, 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. To prevent this, we have taken to temporarily cache the images so

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 for the price (in credits) of various API endpoints. We offer volume pricing for our Enterprise plansYou have to be an existing paying customer to get

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 return Skills data in our Person Profile API endpoint.

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 1000 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). 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 profile is missing a public