faq

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

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

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

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.

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,

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

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

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

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 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

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

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

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

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

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

No, Proxycurl's Linkedin API only scrapes public Linkedin profiles. Contact information of profiles are not present on these public profile pages, so we are not able to provide that information as well. However,

Disclaimer: This article does not, by any means, constitute legal advice. Views expressed are purely opinion and are not legally binding. Consult with your local legal counsel for advice specific to your project,