This week, we dropped an update with some changes you might like. I will also be sending these "changelog" updates a bit more frequently so you can keep abreast. You can also track these changelog articles under the changelog tag on our blog.
We added a new attribute called follower_count which will allow you to track a person's follower count on the platform to the Response of our .
For a long time, users kept asking us how they could associate a callback made from a Work Email Lookup request with the correct profile. My answer has always been to append the corresponding user's profile URL to the parameters of the callback URL.
However, a lot of people still found this confusing. So, we decided to append the requested professional networks Profile URL to the body of the webhook request under the profile_url attribute.
This should make it easier for you to associate a callback with a person profile requested through our Work Email Lookup API Endpoint.
We have an Employee Count API endpoint which used to read cached data from LinkDB. We have updated it to include the use_cache parameter, which offers a freshness guarantee like our Person and Company Profile API endpoints.
You can now call the Employee Count API Endpoint and get fresh data back.
Yes, we have a new dashboard, in case you have not noticed. Today, we added Multiple API key support to the new dashboard. Multiple API keys are useful for users who wish to segregate their Enrich Layer use via API keys.
This feature is, however, locked behind a subscription wall. You need a minimum subscription plan of $299/mo to unlock this feature.
This feature is generally available today.
We added a country filter to the Employee Listing and Employee Search API endpoints. This parameter allows you to further filter employee results on a country level.
You can now enrich profiles in the same API call within the Employee Listing and Search API endpoints by appending the enrich_ parameter. This will return you full cached profiles of each employee returned. If you require fresh profiles, you do need to make a separate API call to our Person Profile Endpoint.
We are working a little harder in marketing and have begun a Build In Public series of blog posts. Here are our recent posts:
I cold-emailed our way to 1M ARR in 18 months. Here's the story.
Revealing our $124 cold-email hack that got us $83333 in monthly recurring revenue
It's not for everybody, but if you enjoy stories about startup struggles, you might enjoy what I have to share about our journey in scaling as a bootstrapped company from time to time.
For the technical crowd, I realized that we could do a lot better in communicating iterations of our product. This is our initial attempt to share the micro improvements that we are pushing out on a weekly basis.
For these content on changelogs, I will be posting it on our blog under the changelog tag.
Lastly [Follow us on Twitter](https://twitter.com/Enrich Layer) if you haven't already. Our Twitter is essentially our API status page. We also share updates on an ad-hoc basis.
