<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: How to connect Twitter data to Splunk in All Apps and Add-ons</title>
    <link>https://community.splunk.com/t5/All-Apps-and-Add-ons/How-to-connect-Twitter-data-to-Splunk/m-p/456336#M56168</link>
    <description>&lt;P&gt;The only difference is the path file, '&lt;A href="https://api.twitter.com/1.1/account_activity/webhooks.json?url=" target="_blank"&gt;https://api.twitter.com/1.1/account_activity/webhooks.json?url=&lt;/A&gt;' so does that mean that my Endpoint URL would change from&lt;BR /&gt;
...account_activity/all/SplunkAPI/webhooks.json to .../account_activity/webhooks.json or remain the same?&lt;/P&gt;

&lt;P&gt;I changed the curl command to read from &lt;A href="https://api.twitter.com/1.1/account_activity/webhooks.json" target="_blank"&gt;https://api.twitter.com/1.1/account_activity/webhooks.json&lt;/A&gt;&lt;BR /&gt;
and did another try that changed the config on Splunk to &lt;A href="https://api.twitter.com/1.1/account_activity/webhooks.json" target="_blank"&gt;https://api.twitter.com/1.1/account_activity/webhooks.json&lt;/A&gt; instead of .../account_activity/all/SplunkAPI/webhooks.json but I was still getting &lt;BR /&gt;
curl: (7) couldn't connect to host for both. &lt;/P&gt;

&lt;P&gt;&lt;STRONG&gt;CODE:&lt;/STRONG&gt;&lt;BR /&gt;
'&lt;A href="https://api.twitter.com/1.1/account_activity/webhooks.jsonurl=https%3A%2F%2Fsplunk.yooza.tcnz.net" target="_blank"&gt;https://api.twitter.com/1.1/account_activity/webhooks.jsonurl=https%3A%2F%2Fsplunk.yooza.tcnz.net&lt;/A&gt;'&lt;BR /&gt;
--header 'authorization: OAuth oauth_consumer_key="OAUTH_1_Client_Key_VALUE", oauth_nonce="GENERATED", oauth_signature="GENERATED", oauth_signature_method="HMAC-SHA1", oauth_timestamp="GENERATED", oauth_token="OAUTH_1_Access_Token_VALUE", oauth_version="1.0"'&lt;/P&gt;</description>
    <pubDate>Wed, 30 Sep 2020 00:35:15 GMT</pubDate>
    <dc:creator>jorubi</dc:creator>
    <dc:date>2020-09-30T00:35:15Z</dc:date>
    <item>
      <title>How to connect Twitter data to Splunk</title>
      <link>https://community.splunk.com/t5/All-Apps-and-Add-ons/How-to-connect-Twitter-data-to-Splunk/m-p/456334#M56166</link>
      <description>&lt;P&gt;Hi team,&lt;/P&gt;

&lt;P&gt;With the new API for Twitter, I've been having difficulty trying to set-up a connection from my host to twitter. &lt;BR /&gt;
QUESTION: Is there a way to connect Twitter to a server?&lt;/P&gt;

&lt;P&gt;Every time I run the curl command on the server, I would get curl: (7) couldn't connect to host. What have I done wrong? &lt;/P&gt;

&lt;P&gt;Thank you for helping! &lt;span class="lia-unicode-emoji" title=":slightly_smiling_face:"&gt;🙂&lt;/span&gt;&lt;/P&gt;

&lt;P&gt;&lt;STRONG&gt;Code:&lt;/STRONG&gt;&lt;BR /&gt;
*Note: I have the actual values for both: &lt;CODE&gt;OAUTH_1_Client_Key_VALUE and OAUTH_1_Access_Token_VALUE&lt;/CODE&gt; hiding for privacy purposes &lt;/P&gt;

&lt;P&gt;curl &lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;--request POST --url 'https://api.twitter.com/1.1/account_activity/all/SplunkAPI/webhooks.jsonurl=https%3A%2F%2Fsplunk.yooza.tcnz.net'
 --header 'authorization: OAuth oauth_consumer_key="OAUTH_1_Client_Key_VALUE", oauth_nonce="GENERATED", oauth_signature="GENERATED", oauth_signature_method="HMAC-SHA1", oauth_timestamp="GENERATED", oauth_token="OAUTH_1_Access_Token_VALUE", oauth_version="1.0"'
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;&lt;STRONG&gt;Configuration:&lt;/STRONG&gt;&lt;BR /&gt;
&lt;EM&gt;In Splunk:&lt;/EM&gt;&lt;BR /&gt;
Data inputs » REST » Twitter&lt;/P&gt;

&lt;P&gt;&lt;STRONG&gt;Endpoint URL&lt;/STRONG&gt;&lt;BR /&gt;
&lt;A href="https://api.twitter.com/1.1/account_activity/all/SplunkAPI/webhooks.json"&gt;https://api.twitter.com/1.1/account_activity/all/SplunkAPI/webhooks.json&lt;/A&gt;&lt;/P&gt;

&lt;P&gt;&lt;STRONG&gt;URL Arguments:&lt;/STRONG&gt; &lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;follow=423424432^stall_warnings=true
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;&lt;EM&gt;In Twitter:&lt;/EM&gt;&lt;/P&gt;

&lt;P&gt;&lt;STRONG&gt;App Name&lt;/STRONG&gt;&lt;BR /&gt;
SplunkAPI&lt;/P&gt;

&lt;P&gt;&lt;STRONG&gt;Website URL&lt;/STRONG&gt;&lt;BR /&gt;
&lt;A href="https://splunk.yooza.tcnz.net"&gt;https://splunk.yooza.tcnz.net&lt;/A&gt; (Is this needed in the technical terms? because we are using a splunk server which wont be avaialble for internet connection)&lt;/P&gt;</description>
      <pubDate>Wed, 15 May 2019 21:51:17 GMT</pubDate>
      <guid>https://community.splunk.com/t5/All-Apps-and-Add-ons/How-to-connect-Twitter-data-to-Splunk/m-p/456334#M56166</guid>
      <dc:creator>jorubi</dc:creator>
      <dc:date>2019-05-15T21:51:17Z</dc:date>
    </item>
    <item>
      <title>Re: How to connect Twitter data to Splunk</title>
      <link>https://community.splunk.com/t5/All-Apps-and-Add-ons/How-to-connect-Twitter-data-to-Splunk/m-p/456335#M56167</link>
      <description>&lt;P&gt;Hi @jorubi,&lt;/P&gt;

&lt;P&gt;The problem is with you curl command. Please use the one from this website : &lt;BR /&gt;
&lt;A href="https://developer.twitter.com/en/docs/accounts-and-users/subscribe-account-activity/quick-start/enterprise-account-activity-api.html"&gt;https://developer.twitter.com/en/docs/accounts-and-users/subscribe-account-activity/quick-start/enterprise-account-activity-api.html&lt;/A&gt;&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;curl --request POST --url 'https://api.twitter.com/1.1/account_activity/webhooks.json?url=&amp;lt;URL&amp;gt;' --header 'authorization: OAuth oauth_consumer_key="&amp;lt;CONSUMER_KEY&amp;gt;", oauth_nonce="GENERATED", oauth_signature="GENERATED", oauth_signature_method="HMAC-SHA1", oauth_timestamp="GENERATED", oauth_token="&amp;lt;ACCESS_TOKEN&amp;gt;", oauth_version="1.0"'
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;Cheers,&lt;BR /&gt;
David&lt;/P&gt;</description>
      <pubDate>Thu, 16 May 2019 07:28:40 GMT</pubDate>
      <guid>https://community.splunk.com/t5/All-Apps-and-Add-ons/How-to-connect-Twitter-data-to-Splunk/m-p/456335#M56167</guid>
      <dc:creator>DavidHourani</dc:creator>
      <dc:date>2019-05-16T07:28:40Z</dc:date>
    </item>
    <item>
      <title>Re: How to connect Twitter data to Splunk</title>
      <link>https://community.splunk.com/t5/All-Apps-and-Add-ons/How-to-connect-Twitter-data-to-Splunk/m-p/456336#M56168</link>
      <description>&lt;P&gt;The only difference is the path file, '&lt;A href="https://api.twitter.com/1.1/account_activity/webhooks.json?url=" target="_blank"&gt;https://api.twitter.com/1.1/account_activity/webhooks.json?url=&lt;/A&gt;' so does that mean that my Endpoint URL would change from&lt;BR /&gt;
...account_activity/all/SplunkAPI/webhooks.json to .../account_activity/webhooks.json or remain the same?&lt;/P&gt;

&lt;P&gt;I changed the curl command to read from &lt;A href="https://api.twitter.com/1.1/account_activity/webhooks.json" target="_blank"&gt;https://api.twitter.com/1.1/account_activity/webhooks.json&lt;/A&gt;&lt;BR /&gt;
and did another try that changed the config on Splunk to &lt;A href="https://api.twitter.com/1.1/account_activity/webhooks.json" target="_blank"&gt;https://api.twitter.com/1.1/account_activity/webhooks.json&lt;/A&gt; instead of .../account_activity/all/SplunkAPI/webhooks.json but I was still getting &lt;BR /&gt;
curl: (7) couldn't connect to host for both. &lt;/P&gt;

&lt;P&gt;&lt;STRONG&gt;CODE:&lt;/STRONG&gt;&lt;BR /&gt;
'&lt;A href="https://api.twitter.com/1.1/account_activity/webhooks.jsonurl=https%3A%2F%2Fsplunk.yooza.tcnz.net" target="_blank"&gt;https://api.twitter.com/1.1/account_activity/webhooks.jsonurl=https%3A%2F%2Fsplunk.yooza.tcnz.net&lt;/A&gt;'&lt;BR /&gt;
--header 'authorization: OAuth oauth_consumer_key="OAUTH_1_Client_Key_VALUE", oauth_nonce="GENERATED", oauth_signature="GENERATED", oauth_signature_method="HMAC-SHA1", oauth_timestamp="GENERATED", oauth_token="OAUTH_1_Access_Token_VALUE", oauth_version="1.0"'&lt;/P&gt;</description>
      <pubDate>Wed, 30 Sep 2020 00:35:15 GMT</pubDate>
      <guid>https://community.splunk.com/t5/All-Apps-and-Add-ons/How-to-connect-Twitter-data-to-Splunk/m-p/456336#M56168</guid>
      <dc:creator>jorubi</dc:creator>
      <dc:date>2020-09-30T00:35:15Z</dc:date>
    </item>
    <item>
      <title>Re: How to connect Twitter data to Splunk</title>
      <link>https://community.splunk.com/t5/All-Apps-and-Add-ons/How-to-connect-Twitter-data-to-Splunk/m-p/456337#M56169</link>
      <description>&lt;P&gt;When I changed both &lt;BR /&gt;
Tried doing it and would get&lt;BR /&gt;
The 403 Forbidden error is an HTTP status code which means that accessing the page or resource you were trying to reach is absolutely forbidden for some reason.&lt;/P&gt;

&lt;P&gt;&lt;STRONG&gt;NEW Endpoint URL&lt;/STRONG&gt;&lt;BR /&gt;
&lt;A href="https://api.twitter.com/1.1/account_activity/webhooks.json" target="_blank"&gt;https://api.twitter.com/1.1/account_activity/webhooks.json&lt;/A&gt; (should this have remained as ...account_activity/all/SplunkAPI/webhooks.json)&lt;/P&gt;

&lt;P&gt;&lt;STRONG&gt;CODE:&lt;/STRONG&gt;&lt;BR /&gt;
'&lt;A href="https://api.twitter.com/1.1/account_activity/webhooks.jsonurl=https%3A%2F%2Fsplunk.yooza.tcnz.net" target="_blank"&gt;https://api.twitter.com/1.1/account_activity/webhooks.jsonurl=https%3A%2F%2Fsplunk.yooza.tcnz.net&lt;/A&gt;'&lt;BR /&gt;
--header 'authorization: OAuth oauth_consumer_key="OAUTH_1_Client_Key_VALUE", oauth_nonce="GENERATED", oauth_signature="GENERATED", oauth_signature_method="HMAC-SHA1", oauth_timestamp="GENERATED", oauth_token="OAUTH_1_Access_Token_VALUE", oauth_version="1.0"'&lt;/P&gt;

&lt;P&gt;Getting these logs on Splunk: http_error_code = 401 error_message = {"errors":[{"code":32,"message":"Could not authenticate you."}]}&lt;/P&gt;

&lt;P&gt;So sorry newb at this. &lt;/P&gt;</description>
      <pubDate>Wed, 30 Sep 2020 00:35:21 GMT</pubDate>
      <guid>https://community.splunk.com/t5/All-Apps-and-Add-ons/How-to-connect-Twitter-data-to-Splunk/m-p/456337#M56169</guid>
      <dc:creator>jorubi</dc:creator>
      <dc:date>2020-09-30T00:35:21Z</dc:date>
    </item>
    <item>
      <title>Re: How to connect Twitter data to Splunk</title>
      <link>https://community.splunk.com/t5/All-Apps-and-Add-ons/How-to-connect-Twitter-data-to-Splunk/m-p/456338#M56170</link>
      <description>&lt;P&gt;Hello @jorubi, is this now working for you ? &lt;/P&gt;</description>
      <pubDate>Mon, 20 May 2019 14:35:25 GMT</pubDate>
      <guid>https://community.splunk.com/t5/All-Apps-and-Add-ons/How-to-connect-Twitter-data-to-Splunk/m-p/456338#M56170</guid>
      <dc:creator>DavidHourani</dc:creator>
      <dc:date>2019-05-20T14:35:25Z</dc:date>
    </item>
    <item>
      <title>Re: How to connect Twitter data to Splunk</title>
      <link>https://community.splunk.com/t5/All-Apps-and-Add-ons/How-to-connect-Twitter-data-to-Splunk/m-p/456339#M56171</link>
      <description>&lt;P&gt;Unfortunately not,  I would get "Received HTTP code 403 from proxy after CONNECT".&lt;BR /&gt;
Also already included export no_proxy=************* in the command&lt;/P&gt;

&lt;P&gt;I have a proxy running on our end.&lt;/P&gt;</description>
      <pubDate>Sun, 26 May 2019 20:16:57 GMT</pubDate>
      <guid>https://community.splunk.com/t5/All-Apps-and-Add-ons/How-to-connect-Twitter-data-to-Splunk/m-p/456339#M56171</guid>
      <dc:creator>jorubi</dc:creator>
      <dc:date>2019-05-26T20:16:57Z</dc:date>
    </item>
    <item>
      <title>Re: How to connect Twitter data to Splunk</title>
      <link>https://community.splunk.com/t5/All-Apps-and-Add-ons/How-to-connect-Twitter-data-to-Splunk/m-p/456340#M56172</link>
      <description>&lt;P&gt;Hi all,&lt;/P&gt;

&lt;P&gt;I've solved the problem by opting for a full archive subscription instead.&lt;BR /&gt;
&lt;A href="https://api.twitter.com/1.1/tweets/search/fullarchive/dev.json"&gt;https://api.twitter.com/1.1/tweets/search/fullarchive/dev.json&lt;/A&gt;&lt;/P&gt;

&lt;P&gt;Now Splunk and Twitter speak to each other. However, this has a limitation of number of requests made. &lt;/P&gt;</description>
      <pubDate>Thu, 30 May 2019 04:45:09 GMT</pubDate>
      <guid>https://community.splunk.com/t5/All-Apps-and-Add-ons/How-to-connect-Twitter-data-to-Splunk/m-p/456340#M56172</guid>
      <dc:creator>jorubi</dc:creator>
      <dc:date>2019-05-30T04:45:09Z</dc:date>
    </item>
    <item>
      <title>Re: How to connect Twitter data to Splunk</title>
      <link>https://community.splunk.com/t5/All-Apps-and-Add-ons/How-to-connect-Twitter-data-to-Splunk/m-p/456341#M56173</link>
      <description>&lt;P&gt;is it free ? &lt;/P&gt;</description>
      <pubDate>Thu, 30 May 2019 05:33:21 GMT</pubDate>
      <guid>https://community.splunk.com/t5/All-Apps-and-Add-ons/How-to-connect-Twitter-data-to-Splunk/m-p/456341#M56173</guid>
      <dc:creator>DavidHourani</dc:creator>
      <dc:date>2019-05-30T05:33:21Z</dc:date>
    </item>
    <item>
      <title>Re: How to connect Twitter data to Splunk</title>
      <link>https://community.splunk.com/t5/All-Apps-and-Add-ons/How-to-connect-Twitter-data-to-Splunk/m-p/456342#M56174</link>
      <description>&lt;P&gt;Hi @jorubi ,&lt;/P&gt;

&lt;P&gt;Thanks for sharing your answer! If it worked, please resolve this post by approving it! If your problem is still not solved, keep us updated so that someone else can help you. &lt;/P&gt;

&lt;P&gt;Thanks for posting!&lt;/P&gt;</description>
      <pubDate>Thu, 06 Jun 2019 21:30:49 GMT</pubDate>
      <guid>https://community.splunk.com/t5/All-Apps-and-Add-ons/How-to-connect-Twitter-data-to-Splunk/m-p/456342#M56174</guid>
      <dc:creator>evania</dc:creator>
      <dc:date>2019-06-06T21:30:49Z</dc:date>
    </item>
    <item>
      <title>Re: How to connect Twitter data to Splunk</title>
      <link>https://community.splunk.com/t5/All-Apps-and-Add-ons/How-to-connect-Twitter-data-to-Splunk/m-p/456343#M56175</link>
      <description>&lt;P&gt;Yes it is but it's not a sustainable solution because there is a threshold of 250 requests. &lt;/P&gt;</description>
      <pubDate>Wed, 12 Jun 2019 23:18:27 GMT</pubDate>
      <guid>https://community.splunk.com/t5/All-Apps-and-Add-ons/How-to-connect-Twitter-data-to-Splunk/m-p/456343#M56175</guid>
      <dc:creator>jorubi</dc:creator>
      <dc:date>2019-06-12T23:18:27Z</dc:date>
    </item>
  </channel>
</rss>

