Steven Goh

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

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

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