Optional.
The ID of an existing status that the update is in reply to.
o Note: This parameter will be ignored unless the author of the tweet this parameter references is mentioned within the status text.
Therefore,
you must include @username,
where username is the author of the referenced tweet,
within the update.

Optional.
The location's latitude that this tweet refers to.
The valid ranges for latitude is -90.0 to +90.0 (North is positive) inclusive.
This parameter will be ignored if outside that range,
if it is not a number,
if geo_enabled is disabled,
or if there not a corresponding long parameter with this tweet.

Optional.
The location's longitude that this tweet refers to.
The valid ranges for longitude is -180.0 to +180.0 (East is positive) inclusive.
This parameter will be ignored if outside that range,
if it is not a number,
if geo_enabled is disabled,
or if there not a corresponding lat parameter with this tweet.

Optional.
By default,
geo-tweets will have their coordinates exposed in the status object (to remain backwards compatible with existing API applications).
To turn off the display of the precise latitude and longitude (but keep the contextual location information),
pass display_coordinates = 0> on the status update.

The first value of the array ($file) is the name of a file to open. The second value ($filename) is the name given to Twitter for the file. If $filename is not provided, the basename portion of $file is used. If $mime_type is not provided, it will be provided automatically using LWP::MediaTypes::guess_media_type().

$raw_image_data can be provided, rather than opening a file, by passing undef as the first array value.

The Tweet text will be rewritten to include the media URL(s), which will reduce the number of characters allowed in the Tweet text. If the URL(s) cannot be appended without text truncation, the tweet will be rejected and this method will return an HTTP 403 error. EOT

);

twitter_api_method oembed => ( description => <<'EOT', Returns information allowing the creation of an embedded representation of a Tweet on third party sites. See the oEmbed specification for information about the response format.

While this endpoint allows a bit of customization for the final appearance of the embedded Tweet, be aware that the appearance of the rendered Tweet may change over time to be consistent with Twitter's Display Requirements. Do not rely on any class or id parameters to stay constant in the returned markup.

twitter_api_method search => ( description => <<'EOT', Returns a HASH reference with some meta-data about the query including the next_page, refresh_url, and max_id. The statuses are returned in results. To iterate over the results, use something similar to:

twitter_api_method direct_messages => ( description => <<'EOT', Returns a list of the 20 most recent direct messages sent to the authenticating user including detailed information about the sending and recipient users.

twitter_api_method sent_direct_messages => ( description => <<'EOT', Returns a list of the 20 most recent direct messages sent by the authenticating user including detailed information about the sending and recipient users.

twitter_api_method show_direct_message => ( description => <<'EOT', Returns a single direct message, specified by an id parameter. Like the direct_messages request, this method will include the user objects of the sender and recipient. Requires authentication.

twitter_api_method new_direct_message => ( description => <<'EOT', Sends a new direct message to the specified user from the authenticating user. Requires both the user and text parameters. Returns the sent message when successful. In order to support numeric screen names, the screen_name or user_id parameters may be used instead of user.

twitter_api_method friends_ids => ( description => <<'EOT', Returns a reference to an array of numeric IDs for every user followed by the specified user. The order of the IDs is reverse chronological.

Use the optional cursor parameter to retrieve IDs in pages of 5000. When the cursor parameter is used, the return value is a reference to a hash with keys previous_cursor, next_cursor, and ids. The value of ids is a reference to an array of IDS of the user's friends. Set the optional cursor parameter to -1 to get the first page of IDs. Set it to the prior return's value of previous_cursor or next_cursor to page forward or backwards. When there are no prior pages, the value of previous_cursor will be 0. When there are no subsequent pages, the value of next_cursor will be 0. EOT

twitter_api_method followers_ids => ( description => <<'EOT', Returns a reference to an array of numeric IDs for every user following the specified user. The order of the IDs may change from call to call. To obtain the screen names, pass the arrayref to "lookup_users".

Use the optional cursor parameter to retrieve IDs in pages of 5000. When the cursor parameter is used, the return value is a reference to a hash with keys previous_cursor, next_cursor, and ids. The value of ids is a reference to an array of IDS of the user's followers. Set the optional cursor parameter to -1 to get the first page of IDs. Set it to the prior return's value of previous_cursor or next_cursor to page forward or backwards. When there are no prior pages, the value of previous_cursor will be 0. When there are no subsequent pages, the value of next_cursor will be 0. EOT

twitter_api_method friendships_incoming => ( description => <<'EOT', Returns an HASH ref with an array of numeric IDs in the ids element for every user who has a pending request to follow the authenticating user. EOT

twitter_api_method friendships_outgoing => ( description => <<'EOT', Returns an HASH ref with an array of numeric IDs in the ids element for every protected user for whom the authenticating user has a pending follow request. EOT

# provided for backwards compatibility twitter_api_method friendship_exists => ( description => <<'EOT', This method is provided for backwards compatibility with Twitter API V1.0. Twitter API V1.1 does not provide an endpoint for this call. Instead, show_friendship is called, the result is inspected, and an appropriate value is returned which can be evaluated in a boolean context.

Tests for the existence of friendship between two users. Will return true if user_a follows user_b, otherwise will return false.

Use of user_a and user_b is deprecated. It has been preserved for backwards compatibility, and is used for the two-argument positional form:

twitter_api_method verify_credentials => ( description => <<'', Returns an HTTP 200 OK response code and a representation of the requesting user if authentication was successful; returns a 401 status code and an error message if not. Use this method to test if supplied user credentials are valid.

twitter_api_method update_profile => ( description => <<'', Sets values that users are able to set under the "Account" tab of their settings page. Only the parameters specified will be updated; to only update the "name" attribute, for example, only include that parameter in your request.

twitter_api_method update_location => ( description => <<'', This method has been deprecated in favor of the update_profile method. Its URL will continue to work, but please consider migrating to the newer and more comprehensive method of updating profile attributes.

twitter_api_method update_profile_background_image => ( description => <<'', Updates the authenticating user's profile background image. The image parameter must be an arrayref with the same interpretation as the image parameter in the update_profile_image method. See that method's documentation for details. The use parameter allows you to specify whether to use the uploaded profile background or not.

twitter_api_method update_profile_colors => ( description => <<'', Sets one or more hex values that control the color scheme of the authenticating user's profile page on twitter.com. These values are also returned in the /users/show API method.

The first value of the array ($file) is the name of a file to open. The second value ($filename) is the name given to Twitter for the file. If $filename is not provided, the basename portion of $file is used. If $mime_type is not provided, it will be provided automatically using LWP::MediaTypes::guess_media_type().

$raw_image_data can be provided, rather than opening a file, by passing undef as the first array value. EOT

twitter_api_method create_block => ( description => <<'', Blocks the user specified in the user_id or screen_name parameter as the authenticating user. Returns the blocked user when successful. You can find out more about blocking in the Twitter Support Knowledge Base.

twitter_api_method lookup_users => ( description => <<'EOT', Return up to 100 users worth of extended information, specified by either ID, screen name, or combination of the two. The author's most recent status (if the authenticating user has permission) will be returned inline. This method is rate limited to 1000 calls per hour.

This method will accept user IDs or screen names as either a comma delimited string, or as an ARRAY ref. It will also accept arguments in the normal HASHREF form or as a simple list of named arguments. I.e., any of the following forms are acceptable:

twitter_api_method show_user => ( description => <<'', Returns extended information of a given user, specified by ID or screen name as per the required id parameter. This information includes design settings, so third party developers can theme their widgets according to a given user's preferences. You must be properly authenticated to request the page of a protected user.

twitter_api_method users_search => ( description => <<'', Run a search for users similar to Find People button on Twitter.com; the same results returned by people search on Twitter.com will be returned by using this API (about being listed in the People Search). It is only possible to retrieve the first 1000 matches from this API.

twitter_api_method get_lists => ( description => <<'', Returns all lists the authenticating or specified user subscribes to, including their own. The user is specified using the user_id or screen_name parameters. If no user is given, the authenticating user is used.

twitter_api_method list_statuses => ( description => <<'', Returns tweet timeline for members of the specified list. Historically, retweets were not available in list timeline responses but you can now use the include_rts=true parameter to additionally receive retweet objects.

twitter_api_method list_memberships => ( description => <<'', Returns the lists the specified user has been added to. If user_id or screen_name are not provided the memberships for the authenticating user are returned.

twitter_api_method members_create_all => ( description => <<'', Adds multiple members to a list, by specifying a reference to an array or a comma-separated list of member ids or screen names. The authenticated user must own the list to be able to add members to it. Note that lists can't have more than 500 members, and you are limited to adding up to 100 members to a list at a time with this method.

twitter_api_method add_list_member => ( description => <<'', Add a member to a list. The authenticated user must own the list to be able to add members to it. Note that lists can't have more than 500 members.

twitter_api_method members_destroy_all => ( description => <<'EOT', Removes multiple members from a list, by specifying a reference to an array of member ids or screen names, or a string of comma separated user ids or screen names. The authenticated user must own the list to be able to remove members from it. Note that lists can't have more than 500 members, and you are limited to removing up to 100 members to a list at a time with this method.

Please note that there can be issues with lists that rapidly remove and add memberships. Take care when using these methods such that you are not too rapidly switching between removals and adds on the same list.

twitter_api_method reverse_geocode => ( description => <<'EOT', Search for places (cities and neighborhoods) that can be attached to a statuses/update. Given a latitude and a longitude, return a list of all the valid places that can be used as a place_id when updating a status. Conceptually, a query can be made from the user's location, retrieve a list of places, have the user validate the location he or she is at, and then send the ID of this location up with a call to statuses/update.

There are multiple granularities of places that can be returned -- "neighborhoods", "cities", etc. At this time, only United States data is available through this method.

Optional. A hint on the "region" in which to search. If a number, then this is a radius in meters, but it can also take a string that is suffixed with ft to specify feet. If this is not passed in, then it is assumed to be 0m. If coming from a device, in practice, this value is whatever accuracy the device has measuring its location (whether it be coming from a GPS, WiFi triangulation, etc.).

Optional. A hint as to the number of results to return. This does not guarantee that the number of results returned will equal max_results, but instead informs how many "nearby" results to return. Ideally, only pass in the number of places you intend to display to the user here.

twitter_api_method geo_search => ( description => <<'EOT', Search for places that can be attached to a statuses/update. Given a latitude and a longitude pair, an IP address, or a name, this request will return a list of all the valid places that can be used as the place_id when updating a status.

Conceptually, a query can be made from the user's location, retrieve a list of places, have the user validate the location he or she is at, and then send the ID of this location with a call to statuses/update.

This is the recommended method to use find places that can be attached to statuses/update. Unlike geo/reverse_geocode which provides raw data access, this endpoint can potentially re-order places with regards to the user who is authenticated. This approach is also preferred for interactive place matching with the user. EOT

twitter_api_method add_place => ( description => <<'EOT', Creates a new place object at the given latitude and longitude.

Before creating a place you need to query similar_places with the latitude, longitude and name of the place you wish to create. The query will return an array of places which are similar to the one you wish to create, and a token. If the place you wish to create isn't in the returned array you can use the token with this method to create a new one. EOT

twitter_api_method trends_place => ( description => <<'', Returns the top 10 trending topics for a specific WOEID. The response is an array of "trend" objects that encode the name of the trending topic, the query parameter that can be used to search for the topic on Search, and the direct URL that can be issued against Search. This information is cached for five minutes, and therefore users are discouraged from querying these endpoints faster than once every five minutes. Global trends information is also available from this API by using a WOEID of 1.

twitter_api_method trends_available => ( description => <<EOT, Returns the locations with trending topic information. The response is an array of "locations" that encode the location's WOEID (a Yahoo! Where On Earth ID http://developer.yahoo.com/geo/geoplanet/) and some other human-readable information such as a the location's canonical name and country.

For backwards compatibility, this method accepts optional lat and long parameters. You should call trends_closest directly, instead.

Use the WOEID returned in the location object to query trends for a specific location. EOT

twitter_api_method trends_closest => ( description => <<EOT, Returns the locations with trending topic information. The response is an array of "locations" that encode the location's WOEID (a Yahoo! Where On Earth ID http://developer.yahoo.com/geo/geoplanet/) and some other human-readable information such as a the location's canonical name and country. The results are sorted by distance from that location, nearest to farthest.

Use the WOEID returned in the location object to query trends for a specific location. EOT

twitter_api_method get_languages => ( description => <<'', Returns the list of languages supported by Twitter along with their ISO 639-1 code. The ISO 639-1 code is the two letter value to use if you include lang with any of your requests.

twitter_api_method get_configuration => ( description => <<'EOT', Returns the current configuration used by Twitter including twitter.com slugs which are not usernames, maximum photo resolutions, and t.co URL lengths.

It is recommended applications request this endpoint when they are loaded, but no more than once a day. EOT

twitter_api_method rate_limit_status => ( description => <<'EOT', Returns the remaining number of API requests available to the authenticated user before the API limit is reached for the current hour.

Use ->rate_limit_status({ authenticate => 0 }) to force an unauthenticated call, which will return the status for the IP address rather than the authenticated user. (Note: for a web application, this is the server's IP address.) EOT

twitter_api_method end_session => ( description => <<'', Ends the session of the authenticating user, returning a null cookie. Use this method to sign users out of client-facing applications like widgets.

twitter_api_method trends_current => ( description => <<'', Returns the current top ten trending topics on Twitter. The response includes the time of the request, the name of each trending topic, and query used on Twitter Search results page for that topic.

twitter_api_method retweeted_to_user => ( description => <<'', Returns the 20 most recent retweets posted by users the specified user follows. The user is specified using the user_id or screen_name parameters. This method is identical to retweeted_to_me except you can choose the user to view. Does not require authentication, unless the user is protected.

twitter_api_method retweeted_by_user => ( description => <<'', Returns the 20 most recent retweets posted by the specified user. The user is specified using the user_id or screen_name parameters. This method is identical to retweeted_by_me except you can choose the user to view. Does not require authentication, unless the user is protected.

twitter_api_method related_results => ( description => <<'', If available, returns an array of replies and mentions related to the specified status. There is no guarantee there will be any replies or mentions in the response. This method is only available to users who have access to #newtwitter. Requires authentication.

twitter_api_method update_profile_banner => ( description => <<'EOT', Uploads a profile banner on behalf of the authenticating user. The image parameter is an arrayref with the following interpretation:

The first value of the array ($file) is the name of a file to open. The second value ($filename) is the name given to Twitter for the file. If $filename is not provided, the basename portion of $file is used. If $mime_type is not provided, it will be provided automatically using LWP::MediaTypes::guess_media_type().

$raw_image_data can be provided, rather than opening a file, by passing undef as the first array value. EOT

BECAUSE THIS SOFTWARE IS LICENSED FREE OF CHARGE, THERE IS NO WARRANTY FOR THE SOFTWARE, TO THE EXTENT PERMITTED BY APPLICABLE LAW. EXCEPT WHEN OTHERWISE STATED IN WRITING THE COPYRIGHT HOLDERS AND/OR OTHER PARTIES PROVIDE THE SOFTWARE "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. THE ENTIRE RISK AS TO THE QUALITY AND PERFORMANCE OF THE SOFTWARE IS WITH YOU. SHOULD THE SOFTWARE PROVE DEFECTIVE, YOU ASSUME THE COST OF ALL NECESSARY SERVICING, REPAIR, OR CORRECTION.

IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MAY MODIFY AND/OR REDISTRIBUTE THE SOFTWARE AS PERMITTED BY THE ABOVE LICENSE, BE LIABLE TO YOU FOR DAMAGES, INCLUDING ANY GENERAL, SPECIAL, INCIDENTAL, OR CONSEQUENTIAL DAMAGES ARISING OUT OF THE USE OR INABILITY TO USE THE SOFTWARE (INCLUDING BUT NOT LIMITED TO LOSS OF DATA OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY YOU OR THIRD PARTIES OR A FAILURE OF THE SOFTWARE TO OPERATE WITH ANY OTHER SOFTWARE), EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.