As the chief customer support officer of Proxycurl, I have been receiving emails seeking clarifications on our service reliability from customers who swing between our service and Mantheos'.
I quote one email:
One of our other vendors informed us there have been significant changes to the LinkedIn data structure. This has broken their ability to pull certain data, particularly around companies.
- Can you let us know if Proxycurl has been affected by these changes?
- If yes, can you tell us which data points are impacted?
- And if the jobs data API has been impacted?
We hope that these changes will not impact Proxycurl and your API. Please let us know as soon as you can.
I asked if it was Mantheos, and this is what the customer said:
As a matter of fact, yes, it is. Why do you ask?
The reason I am writing this post is to get the facts straight.
- Mantheos has stated that there are significant changes to LinkedIn's data structure. However, based on our understanding, there are no changes to LinkedIn's data structure. You can verify this is true by browsing LinkedIn. Everything that is there is still there.
- LinkedIn is currently suing Mantheos.
- Mantheos' method of scraping LinkedIn is actively pursued and shut down by LinkedIn.
If you are using Mantheos, that means you are:
- Not GDPR or CCPA compliant.
- Utilizing (alleged) fraudulently obtained private LinkedIn profile data.
Please don't take my word for it. Read LinkedIn's legal docket against Mantheos here.
Proxycurl, on the flip side:
- Works with public LinkedIn profiles only. We do not scrape private LinkedIn profiles. And that means that
- We do not log into LinkedIn.
- We do not break Recaptchas.
- We do not use fake, fraudulent debit cards to make fake purchases of LinkedIn Sales Navigator.
Switch to Proxycurl today, and don't get yourself sued by LinkedIn. Instead, send us an email at [email protected], and we will be happy to match your package with Mantheos.