faq

Short answer, yes. Long answer, It depends on the plan you are on There are three types of plans Proxycurl offers: 1. Monthly Plan, with 12-month contract 2. Annual Plan, with 12-month contract 3. Pay-as-you-go, ala-carte credit purchase The 2nd and 3rd types won't be the content of discussion here

Proxycurl's Employee Listing Endpoint and the Search API are powered by LinkDB. This means that searches are performed within LinkDB. We do not scrape LinkedIn for employee data or to perform people/company searches. Since LinkDB is not synced with the latest data on LinkedIn, you might experience: 1. Some

We have been listening to your feedback and compliments, and we heard how much you've been loving Proxycurl. Thus the launch of our "Tweet for credits" initiative that serves to reward customers like yourself! What is it about? Simply tweet (or post in the terms of x.com) and you'll

We often receive inquiries about enabling CORS headers to allow any origin to access the Proxycurl API. However, our policy is to deliberately block requests to the Proxycurl API that are made from a browser client. The reason for this is that it would require exposing the Proxycurl API key

We have three similar API endpoints that seem to perform the same function—these are the Employee Search Endpoint, the Person Search Endpoint, and the Role Lookup Endpoint. However, in actuality, each one has unique nuances. * Employee Search Endpoint - Powered by LinkDB, this endpoint returns a list of employees

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 with details so we can come back to you with an appropriate response: * Please

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 the Activity response section of Person Profile Endpoint For companies, our Company Profile API follows the following: * updates - See CompanyUpdate response section of Company Profile Endpoint Do note that