Twittex.API
Twitter API wrapper.
Provides convenience functions for working with Twitter’s RESTful API.
You can use head/3
, get/3
, post/4
, put/4
, patch/4
, delete/3
and
others using a relative url pointing to the API endpoint. For example:
iex> API.get! "/search/tweets.json?q=%23myelixirstatus"
%HTTPoison.Response{}
Authentication
Under the hood, the Twittex.API
module uses HTTPoison.Base
and overrides the
request/5
method to add support for following OAuth authentication method:
- xAuth authentication with user credentials.
- Application-only authentication based on the OAuth 2 specification.
To request an access token with one of the method listed above. See get_token/1
and get_token/3
. Here, a brief example:
iex> token = API.get_token!
%OAuth2.AccessToken{}
With Application-only authentication you don’t have the context of an authenticated user and this means that any request to API for endpoints that require user context, such as posting tweets, will not work.
Twitter requires clients accessing their API to be authenticated. This means that you must provide an authentication token for each request.
This can be done by passing an OAuth token as a value of the :auth
option:
iex> API.get! "/statuses/home_timeline.json", [], auth: token
%HTTPoison.Response{}
Summary
Functions
Issues a DELETE request to the given url
Issues a DELETE request to the given url, raising an exception in case of failure
Issues a GET request to the given url
Issues a GET request to the given url, raising an exception in case of failure
Request an [Application-only authentication] token
Request a user specific ([xAuth]) authentication token
Same as get_token/1
but raises OAuth2.Error
if an error occurs during the
request
Same as get_token/3
but raises HTTPoison.Error
if an error occurs during the
request
Issues a HEAD request to the given url
Issues a HEAD request to the given url, raising an exception in case of failure
Issues an OPTIONS request to the given url
Issues a OPTIONS request to the given url, raising an exception in case of failure
Issues a PATCH request to the given url
Issues a PATCH request to the given url, raising an exception in case of failure
Issues a POST request to the given url
Issues a POST request to the given url, raising an exception in case of failure
Issues a PUT request to the given url
Issues a PUT request to the given url, raising an exception in case of failure
Issues an HTTP request with the given method to the given url
Issues an HTTP request with the given method to the given url, raising an exception in case of failure
Starts HTTPoison and its dependencies
Types
headers :: [{binary, binary}]
Functions
Specs
Issues a DELETE request to the given url.
Returns {:ok, response}
if the request is successful, {:error, reason}
otherwise.
See request/5
for more detailed information.
Issues a DELETE request to the given url, raising an exception in case of failure.
If the request does not fail, the response is returned.
See request!/5
for more detailed information.
Specs
Issues a GET request to the given url.
Returns {:ok, response}
if the request is successful, {:error, reason}
otherwise.
See request/5
for more detailed information.
Issues a GET request to the given url, raising an exception in case of failure.
If the request does not fail, the response is returned.
See request!/5
for more detailed information.
Specs
get_token(Keyword.t) ::
{:ok, OAuth2.AccessToken.t} |
{:error, OAuth2.Error.t}
Request an Application-only authentication token.
Returns {:ok, token}
if the request is successful, {:error, reason}
otherwise.
With Application-only authentication you don’t have the context of an authenticated user and this means that any request to API for endpoints that require user context, such as posting tweets, will not work.
Specs
Request a user specific (xAuth) authentication token.
Returns {:ok, token}
if the request is successful, {:error, reason}
otherwise.
xAuth provides a way for applications to exchange a username and password for an OAuth access token. Once the access token is retrieved, the application should dispose of the login and password corresponding to the user.
Specs
get_token!(Keyword.t) :: OAuth2.AccessToken.t
Same as get_token/1
but raises OAuth2.Error
if an error occurs during the
request.
Same as get_token/3
but raises HTTPoison.Error
if an error occurs during the
request.
Specs
Issues a HEAD request to the given url.
Returns {:ok, response}
if the request is successful, {:error, reason}
otherwise.
See request/5
for more detailed information.
Issues a HEAD request to the given url, raising an exception in case of failure.
If the request does not fail, the response is returned.
See request!/5
for more detailed information.
Specs
Issues an OPTIONS request to the given url.
Returns {:ok, response}
if the request is successful, {:error, reason}
otherwise.
See request/5
for more detailed information.
Issues a OPTIONS request to the given url, raising an exception in case of failure.
If the request does not fail, the response is returned.
See request!/5
for more detailed information.
Specs
Issues a PATCH request to the given url.
Returns {:ok, response}
if the request is successful, {:error, reason}
otherwise.
See request/5
for more detailed information.
Specs
Issues a PATCH request to the given url, raising an exception in case of failure.
If the request does not fail, the response is returned.
See request!/5
for more detailed information.
Specs
Issues a POST request to the given url.
Returns {:ok, response}
if the request is successful, {:error, reason}
otherwise.
See request/5
for more detailed information.
Issues a POST request to the given url, raising an exception in case of failure.
If the request does not fail, the response is returned.
See request!/5
for more detailed information.
Specs
Issues a PUT request to the given url.
Returns {:ok, response}
if the request is successful, {:error, reason}
otherwise.
See request/5
for more detailed information.
Issues a PUT request to the given url, raising an exception in case of failure.
If the request does not fail, the response is returned.
See request!/5
for more detailed information.
Specs
Issues an HTTP request with the given method to the given url.
This function is usually used indirectly by get/3
, post/4
, put/4
, etc
Args:
method
- HTTP method as an atom (:get
,:head
,:post
,:put
,:delete
, etc.)url
- target url as a binary string or char listbody
- request body. See more belowheaders
- HTTP headers as an orddict (e.g.,[{"Accept", "application/json"}]
)options
- Keyword list of options
Body:
- binary, char list or an iolist
{:form, [{K, V}, ...]}
- send a form url encoded{:file, "/path/to/file"}
- send a file
Options:
:timeout
- timeout to establish a connection, in milliseconds. Default is 8000:recv_timeout
- timeout used when receiving a connection. Default is 5000:stream_to
- a PID to stream the response to:proxy
- a proxy to be used for the request; it can by a regular url or a{Host, Proxy}
tuple:proxy_auth
- proxy authentication{User, Password}
tuple:ssl
- SSL options supported by thessl
erlang module:follow_redirect
- a boolean that causes redirects to be followed:max_redirect
- an integer denoting the maximum number of redirects to follow
Timeouts can be an integer or :infinity
This function returns {:ok, response}
or {:ok, async_response}
if the
request is successful, {:error, reason}
otherwise.
Examples
request(:post, "https://my.website.com", "{\"foo\": 3}", [{"Accept", "application/json"}])
Issues an HTTP request with the given method to the given url, raising an exception in case of failure.
request!/5
works exactly like request/5
but it returns just the
response in case of a successful request, raising an exception in case the
request fails.