​
What are Webhooks?

Webhooks let external services push tweet data directly to GenX. This is how TwitterAPI.io sends matching tweets to your account in real-time.

​
How It Works

  1. You create a campaign on GenX with filter rules
  2. GenX creates a corresponding filter rule on TwitterAPI.io
  3. TwitterAPI.io monitors Twitter and sends matching tweets to GenX’s webhook
  4. GenX receives the tweet, matches it to your campaign, and adds it to your queue
This happens automatically — you don’t need to configure webhooks manually.

​
Webhook URL

Your GenX webhook endpoint: 
https://twitter.companylogos.in/api/webhook/tweets
This URL is pre-configured in TwitterAPI.io. Tweets are routed to the correct user based on the rule tag (which matches your campaign name).

​
Custom Webhook Integration

If you have your own tweet source, you can send data to GenX’s webhook with a token: 
POST /api/webhook/tweets?token=YOUR_WEBHOOK_SECRET

​
Payload Format

{
  "tweets": [
    {
      "id": "tweet-id",
      "text": "The tweet content",
      "author": {
        "userName": "handle",
        "name": "Display Name",
        "profilePicture": "https://..."
      }
    }
  ]
}
Also supports: { "data": [...] }, bare arrays, or single tweet objects.

​
Getting Your Webhook Secret

  1. Go to Settings
  2. Find your Webhook Secret
  3. Copy it and append as ?token=SECRET to the webhook URL

​
Troubleshooting

Check that your campaign name exactly matches the rule tag in TwitterAPI.io. The match is case-insensitive.
You’re using a custom integration without a token. Add ?token=YOUR_SECRET to the URL.
Each campaign name must be unique across all users. If two users have a campaign named “seo”, tweets may route incorrectly.