Recommendation posts are useful because the person explains what they need in public. A clear post about a tool, service, repair, class, or venue gives you more context than a cold contact list.
SocialListeningAPI searches public Facebook posts by keyword and returns normalized post data with source URLs. It does not search private content or provide native outreach, lead scoring, scheduling, or CRM delivery.
Step 1: Write Facebook lead generation queries
Create a SocialListeningAPI account, claim the 100 free credits, and copy the API key.
Combine a request phrase with the exact product or problem:
can anyone recommend servicelooking for product categoryalternative to competitorneed help with problembest tool for task
Use several narrow queries instead of one broad industry word. Add a place name when location is part of the buying decision.
Step 2: Search public Facebook posts
Run the approved phrase through the live endpoint:
curl --get 'https://api.sociallisteningapi.com/api/v1/facebook/search' \
--data-urlencode 'query=can anyone recommend an accounting tool' \
--header 'x-api-key: YOUR_API_KEY'
Each successful Facebook search costs 7 credits. The current endpoint returns one page and no next cursor. The Facebook search API covers current fields and limits.
Step 3: Build the external lead queue
Store the post ID or URL, query, author details, published date, text, first-seen time, and reason for the match in an external sheet or CRM. Skip duplicate URLs. A person should open the source and confirm the request is current and relevant.
Do not infer location, purchase intent, or urgency when the post does not state it. Facebook search does not return private or closed-group content, comment text, or a complete history of Facebook activity.
Step 4: Respond with context
Answer the request before mentioning a product. Refer to the need stated in the post and disclose your connection when recommending your own company. Skip old, unrelated, or poor-fit posts.
Replies, DMs, contact enrichment, and follow-up happen outside SocialListeningAPI and should stay under human control.
Conclusion
The expected output is a small queue containing the public post, author, date, source URL, and reason it may be useful. Ten well-matched posts are easier to review than hundreds of broad Facebook name matches.
Continue with How to Find Leads on Reddit Without Spamming.




