faq

Proxycurl API In general, we will refund you if you accidentally purchase credits and spend at most 10 of them. Refunds are granted once per customer. There are three scenarios in which a refund will be provided: 1. A new order has been made (e.g. you bought too many

LinkedIn connections are not part of the public profile data set, and we only work with public data. Therefore, LinkedIn connections are not available for us to scrape and we do not scrape them. No, we do not provide LinkedIn connection data.

We do not offer any discounts to any classes of organizations.

There is not a maximum length for individual parameters of a search query; rather, your entire query must be at most 4094 characters.

In our API, a 404 is considered a successful query, despite being classified as an error code. You can check our API reference manual sections on credits and status codes for official documentation at any time, but here we will explain the why of this policy. When a request comes

1. Our Employee/Student Listing API endpoint relies on LinkDB, a database that exclusively gathers public LinkedIn profiles. Consequently, the data we can provide is only as comprehensive as the content available in LinkDB. 2. LinkedIn's specific heuristics for associating an individual with their employer are not transparent to us.

The Reverse Work Email Lookup API endpoint is a search function designed to return the closest match. However, the Reverse Email Lookup can sometimes return false positives. Even Google's search results can be inaccurate at times. It's important to understand that the Reverse Work Email Lookup doesn't actually search a

Yes, you are. Each API call you make is an independent call to our servers, and we bill you each time you make a call. The reality is that running our servers is expensive, and every time you make a request, we do the work to process your request, even

This bug has now been fixed! You should always get consistent results when using the Lookup endpoints in the same way. Note that changing the value of similarity_checks may change affect the answer, since this parameter affects how the query behaves as well as any temporarily-cached data. Original answer

You might get an erroneous HTTP status code of 503 when you call our API occasionally. This is due to a temporary error. There are many reasons for this: * It could be due to a network error between our internal services or web scraping infrastructure. * It could be due to

There will always be bugs with Proxycurl API, so sometimes, the API might not be behaving in a way that is predictable for you. You might want to find out why. Please provide our customer support [[email protected]] with details so we can come back to you with an

This post applies to the following API endpoints: * Company Lookup Endpoint [https://nubela.co/proxycurl/linkedin/company] * Role Lookup Endpoint [https://nubela.co/proxycurl/docs#people-api-role-lookup-endpoint] * Person Lookup Endpoint [https://nubela.co/proxycurl/linkedin] * Work Email Lookup Endpoint [https://nubela.co/proxycurl/email-lookup] Occasionally, our Lookup API endpoints return the

For people profiles, our Person Profile API offers the following: * articles - Articles posted by the user * activities -  see https://nubela.co/proxycurl/docs#people-api-person-profile-endpoint-response-activity For companies, our Company Profile API follows the following: * updates - See https://nubela.co/proxycurl/docs#company-api-company-profile-endpoint-response-companyupdate Do note that we are only

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 profiles

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