How to Find Sales Opportunities on X With an API

Questions on X go stale fast. A post asking for a tool today may be buried under hundreds of replies by next week.

This Twitter lead generation workflow searches recent public X posts, removes weak matches, and gives you a small queue to review while the discussion is still active.

SocialListeningAPI searches public posts on X for the phrases you choose and returns normalized records with source URLs.

Step 1: Create your API key

Sign up for SocialListeningAPI, claim the 100 free credits, and copy your API key. Keep it in a server-side environment variable.

The Twitter search API page explains how X post search works and what data it returns.

Step 2: Search for a clear action

Use phrases that reveal what the author wants:

• recommend an analytics API
• looking for a social listening tool
• alternative to competitor name
• how to search LinkedIn posts
• need help tracking brand mentions

Avoid one-word category searches. They return news, promotions, and posts with no useful problem.

Step 3: Run the Twitter lead generation search

Send one phrase to the X post search endpoint:

curl --get 'https://api.sociallisteningapi.com/api/v1/x/search' \
  --data-urlencode 'query=looking for a social listening tool' \
  --header 'x-api-key: YOUR_API_KEY'

Each successful request costs 1 credit. Results are returned newest first in data.items.

{
  "data": {
    "items": [
      {
        "url": "https://x.com/username/status/post-id",
        "content": { "text": "Post text" },
        "author": { "display_name": "Author name" },
        "published_at": "2026-08-07T01:30:00.000Z",
        "ext": { "conversation_id": "post-id", "language": "en" }
      }
    ]
  },
  "credits_used": 1
}

Use content.text for the problem, url for review, and published_at to remove old posts.

Step 4: Create a recent review queue

Store post IDs or URLs outside SocialListeningAPI and skip anything already handled. Keep a result when it asks for a recommendation, describes a current problem, or compares products you know.

Your scheduler, storage, and any LLM classification run outside the API.

Step 5: Reply while the post is useful

Read the whole thread first. Answer the question, explain why your suggestion fits, and disclose your connection if you mention your product. Do not automate replies or force a pitch into unrelated posts.

Conclusion

Start with five phrases and one daily run. If you later run six searches three times each weekday, the workflow uses up to 90 credits per week.

Keep the final queue short and recent. Ten posts you can review properly are more useful than a long feed you will never read.

Continue with Find New Product Launches That Need Agency Help.

Written by ShashFounder at sociallisteningapi, focused on product and growth