API-Twitter
view release on metacpan or search on metacpan
README.mkdn view on Meta::CPAN
# METHODS
## action
my $result = $twitter->action($verb, %args);
# e.g.
$twitter->action('head', %args); # HEAD request
$twitter->action('options', %args); # OPTIONS request
$twitter->action('patch', %args); # PATCH request
The action method issues a request to the API resource represented by the
object. The first parameter will be used as the HTTP request method. The
arguments, expected to be a list of key/value pairs, will be included in the
request if the key is either `data` or `query`.
## create
my $results = $twitter->create(%args);
# or
$twitter->POST(%args);
The create method issues a `POST` request to the API resource represented by
the object. The arguments, expected to be a list of key/value pairs, will be
included in the request if the key is either `data` or `query`.
## delete
my $results = $twitter->delete(%args);
# or
$twitter->DELETE(%args);
The delete method issues a `DELETE` request to the API resource represented by
the object. The arguments, expected to be a list of key/value pairs, will be
included in the request if the key is either `data` or `query`.
## fetch
my $results = $twitter->fetch(%args);
# or
$twitter->GET(%args);
The fetch method issues a `GET` request to the API resource represented by the
object. The arguments, expected to be a list of key/value pairs, will be
included in the request if the key is either `data` or `query`.
## update
my $results = $twitter->update(%args);
# or
$twitter->PUT(%args);
The update method issues a `PUT` request to the API resource represented by
the object. The arguments, expected to be a list of key/value pairs, will be
included in the request if the key is either `data` or `query`.
# RESOURCES
## account
$twitter->account;
The account method returns a new instance representative of the API
resource requested. This method accepts a list of path segments which will be
used in the HTTP request. The following documentation can be used to find more
information. [https://dev.twitter.com/rest/public#account](https://dev.twitter.com/rest/public#account).
## application
$twitter->application;
The application method returns a new instance representative of the API
resource requested. This method accepts a list of path segments which will be
used in the HTTP request. The following documentation can be used to find more
information. [https://dev.twitter.com/rest/public#application](https://dev.twitter.com/rest/public#application).
## blocks
$twitter->blocks;
The blocks method returns a new instance representative of the API
resource requested. This method accepts a list of path segments which will be
used in the HTTP request. The following documentation can be used to find more
information. [https://dev.twitter.com/rest/public#blocks](https://dev.twitter.com/rest/public#blocks).
## direct\_messages
$twitter->direct_messages;
The direct\_messages method returns a new instance representative of the API
resource requested. This method accepts a list of path segments which will be
used in the HTTP request. The following documentation can be used to find more
information. [https://dev.twitter.com/rest/public#direct\_messages](https://dev.twitter.com/rest/public#direct_messages).
## favorites
$twitter->favorites;
The favorites method returns a new instance representative of the API
resource requested. This method accepts a list of path segments which will be
used in the HTTP request. The following documentation can be used to find more
information. [https://dev.twitter.com/rest/public#favorites](https://dev.twitter.com/rest/public#favorites).
## followers
$twitter->followers;
The followers method returns a new instance representative of the API
resource requested. This method accepts a list of path segments which will be
used in the HTTP request. The following documentation can be used to find more
information. [https://dev.twitter.com/rest/public#followers](https://dev.twitter.com/rest/public#followers).
## friends
( run in 0.814 second using v1.01-cache-2.11-cpan-39bf76dae61 )