Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    text
    copied!<p><a href="http://www.nuget.org/packages/Microsoft.Owin.Security.Twitter/" rel="nofollow noreferrer">Microsoft.Owin.Security.Twitter</a> for authentication + custom C# code with <a href="http://www.nuget.org/packages/Microsoft.Net.Http/" rel="nofollow noreferrer">HttpClient</a> and <a href="http://www.nuget.org/packages/Newtonsoft.Json/" rel="nofollow noreferrer">Json.NET</a></p> <p>Something like:</p> <pre><code>using (var client = new HttpClient()) { client.BaseAddress = new Uri("https://api.twitter.com/1.1/"); client.DefaultRequestHeaders.Authorization = authValue; var response = await client.GetAsync("search/tweets.json"); if (response.IsSuccessStatusCode) { var json = await response.Content.ReadAsStringAsync(); var tweets = JsonConvert.DeserializeObject&lt;Tweets&gt;(json); } } </code></pre> <p>Good read:</p> <ul> <li><a href="http://blogs.msdn.com/b/henrikn/archive/2012/02/16/extending-httpclient-with-oauth-to-access-twitter.aspx" rel="nofollow noreferrer">Extending HttpClient with OAuth to Access Twitter</a> (Feb, 2012)</li> <li><a href="http://www.asp.net/web-api/overview/advanced/calling-a-web-api-from-a-net-client" rel="nofollow noreferrer">Calling a Web API From a .NET Client (C#)</a></li> <li>Official documentation: <a href="https://dev.twitter.com/oauth" rel="nofollow noreferrer">OAuth API</a>, <a href="https://dev.twitter.com/rest/public" rel="nofollow noreferrer">REST API</a>, <a href="https://dev.twitter.com/streaming/overview" rel="nofollow noreferrer">Streaming API</a></li> </ul>
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload