Home / Use cases / How senderpools.com uses social data + build your own with…
How senderpools.com uses social data + build your own with Scrapall
senderpools.com describes itself on its website as "Sender Pools is cold email infrastructure with free domains, free Google, Microsoft and SMTP mailboxes, automatic warmup and rotation. Pay per send, not per mailbox". Products like senderpools.com depend on public social data. With Scrapall you can pull the same kind of public data from LinkedIn, LinkedIn Ad Library through 8 REST endpoints and build your own version.
Updated · by the Scrapall team
Platforms and endpoints
| Product | Platform | Endpoint | What it returns |
|---|---|---|---|
| senderpools.com | LinkedIn Ad Library | /v1/linkedin/ad | Ad Details |
| senderpools.com | LinkedIn Ad Library | /v1/linkedin/ads_search | Search Ads |
| senderpools.com | /v1/linkedin/company | Company Page | |
| senderpools.com | /v1/linkedin/company_posts | Company Posts | |
| senderpools.com | /v1/linkedin/post | Post | |
| senderpools.com | /v1/linkedin/post_captions | Post Transcript | |
| senderpools.com | /v1/linkedin/user | Person's Profile | |
| senderpools.com | /v1/linkedin/search_posts | Search Posts |
Example request
Every endpoint is a plain HTTPS GET or POST with your key in the X-Scapi-Key header. Responses are JSON.
curl "https://api.scrapall.bipsport.com/scapi/v1/linkedin/ad?url=https://www.linkedin.com/ad-library/detail/666281156" \
-H "X-Scapi-Key: YOUR_API_KEY"What you can build
To build a tool in the same space as senderpools.com, collect public social data from LinkedIn, LinkedIn Ad Library with the endpoints below, keep the responses in your own database, and add the analysis or workflow your users pay for. The facts about senderpools.com on this page come from the sources listed at the bottom.
How to build it, step by step
- Get an API key on the Buy page; new accounts start with 20 free credits.
- Call /v1/linkedin/ad first to check the response fields you need.
- Add the other endpoints (/v1/linkedin/ads_search, /v1/linkedin/company, /v1/linkedin/company_posts) and store each JSON response with a timestamp.
- Schedule the collector (cron or a queue) and build the view or alert on top of the stored data.
FAQ
Which platforms does this use case need?
It uses public data from LinkedIn, LinkedIn Ad Library, all reachable through one Scrapall API key.
How do I authenticate the requests?
Send your key in the X-Scapi-Key header on every request. Responses are JSON.
How much does it cost to start?
New accounts get 20 free credits. After that you pay per request in USDT; see the Pricing page.
Can I run it on a schedule?
Yes. Each endpoint is a plain HTTPS call, so a cron job or queue worker can collect fresh data every day.