Changelog
Follow up on the latest improvements and updates.
RSS
We have a couple of important updates to share,
going into effect today.
➤
Charging for 404s on LinkedIn URLs
We will now charge 1 credit for 404 (not found) responses on all live scraping endpoints, except for our person match and company search endpoints (see table below). This change better aligns with our costs, as we must perform a live scrape to return a 404 response.
➤
Improved Company Data Handling
The company object in the person profile endpoint now has a 3-month cache period, while person data remains uncached. This reduces the number of LinkedIn scrapes, improving stability and performance overall. If you need the most up-to-date company profile, you can always retrieve it via the dedicated company endpoint (https://api.scrapin.io/v1/enrichment/company).
➤
Fixes
- Employee Count Range on Company Profiles (via dedicated endpoint)
- Language Proficiency Levels on Profiles
We’re excited to announce improvements to two of our core API endpoints:
What’s new in v1.1.0?
POST method:
We’ve transitioned from GET
to POST
for more flexibility and security.Boolean filters:
You can now use true/false
flags in the request body to retrieve only the data you need.These changes bring faster response times and more efficient API usage, especially when working with large datasets or customized output needs.
Explore the new documentation here: https://docs.scrapin.io/introduction
Credit usage remains the same:
Regardless of how many boolean fields you enable in your request, each API call still costs just 1 credit.
Deprecation notice:
The previous version (v0) will be deprecated in 3 months, so we recommend updating your integrations soon.