Find Early Adopters on Hacker News With an API

Hacker News users describe technical problems in detail. That makes Ask HN questions, Show HN launches, and comments useful for finding people who may test an early developer product.

This workflow builds a research list. It does not automate comments or treat every HN user as a lead.

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

Step 1: Get your API key

Create a SocialListeningAPI account and claim the 100 free credits. The Hacker News API guide covers the normalized fields and how this search differs from the official HN API.

Step 2: Choose technical problem searches

Start with six phrases tied to your product:

• Ask HN social listening
• Show HN developer analytics
• recommend an API monitoring tool
• how do you track product mentions
• open source social data
• alternative to competitor name

Search the problem and the workaround, not only your product category.

Step 3: Search with the Hacker News API

Run the Hacker News search endpoint:

curl --get 'https://api.sociallisteningapi.com/api/v1/hackernews/search' \
  --data-urlencode 'query=Show HN developer analytics' \
  --header 'x-api-key: YOUR_API_KEY'

The endpoint searches indexed HN stories and comments, newest first. One successful search costs 1 credit.

{
  "data": {
    "items": [
      {
        "url": "https://news.ycombinator.com/item?id=item-id",
        "content": { "title": "Show HN title", "text": "Post or comment text" },
        "author": { "display_name": "username" },
        "published_at": "2026-08-07T01:30:00.000Z"
      }
    ]
  },
  "credits_used": 1
}

Step 4: Group results by use case

Save source URL, author, title, text, date, and one use-case label in a spreadsheet or database. Storage and grouping happen outside SocialListeningAPI.

Keep results where someone explains a problem, ships an adjacent product, or asks how others handle the task. Skip generic news and old comments without enough context.

Step 5: Ask for feedback with context

Read the full HN thread before contacting anyone. For a Show HN launch, discuss the product and the shared technical problem. For a question, give a complete answer before mentioning your work.

Conclusion

Try one Ask HN phrase and one Show HN phrase before building a longer search list. If an external scheduler runs six searches each weekday, it uses up to 30 credits per week.

Keep technical context beside every source. That context should tell you whether the person fits and give you something useful to discuss in the first conversation.

Continue with Detect Emerging Category Terms.

Written by ShashFounder at sociallisteningapi, focused on product and growth