Home / Use cases / How briefos.ai uses social data + build your own with…
How briefos.ai uses social data + build your own with Scrapall
briefos.ai describes itself on its website as "briefOS reads why an ad won, block by block, and turns it into a brief for your product. Spy library, your Meta account, teardowns, briefs. Free for 7 days. The first 250 accounts get 50% off for life". Products like briefos.ai depend on public social data. With Scrapall you can pull the same kind of public data from Facebook Ad Library, Facebook Events through 8 REST endpoints and build your own version.
Updated · by the Scrapall team
Platforms and endpoints
| Product | Platform | Endpoint | What it returns |
|---|---|---|---|
| briefos.ai | Facebook Ad Library | /v1/facebook/ads_ad | Ad Details |
| briefos.ai | Facebook Ad Library | /v1/facebook/ads_ad_captions | Ad Transcript |
| briefos.ai | Facebook Ad Library | /v1/facebook/ads_company_ads | Company Ads |
| briefos.ai | Facebook Ad Library | /v1/facebook/ads_search_ads | Search |
| briefos.ai | Facebook Ad Library | /v1/facebook/ads_search_companies | Search for Companies |
| briefos.ai | Facebook Events | /v1/facebook/event_details | Event Details |
| briefos.ai | Facebook Events | /v1/facebook/events | Events |
| briefos.ai | Facebook Events | /v1/facebook/events_search | Search Events |
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/facebook/ads_ad" \
-H "X-Scapi-Key: YOUR_API_KEY"What you can build
To build a tool in the same space as briefos.ai, collect public social data from Facebook Ad Library, Facebook Events with the endpoints below, keep the responses in your own database, and add the analysis or workflow your users pay for. The facts about briefos.ai 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/facebook/ads_ad first to check the response fields you need.
- Add the other endpoints (/v1/facebook/ads_ad_captions, /v1/facebook/ads_company_ads, /v1/facebook/ads_search_ads) 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 Facebook Ad Library, Facebook Events, 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.