| Namespace | http://repository.mulesoft.org/releases/org/mule/modules/mule-module-twitter |
|---|---|
| Schema Location | http://repository.mulesoft.org/releases/org/mule/modules/mule-module-twitter/2.3/mule-twitter.xsd |
| Version | 2.3 |
| Minimum Mule Version | 3.2 |
A Connector for Twitter which uses twitter4j.
| Configuration | |||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
Configure an instance of this module
| |||||||||||
| Message Processors | |||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
Creates a new place at the given latitude and longitude.
| |||||||||||
Destroys the status specified by the required ID parameter.
| |||||||||||
Returns the current top 10 trending topics on Twitter.
| |||||||||||
Returns the top 20 trending topics for each hour in a given day.
| |||||||||||
Find out more details of a place that was returned from the reverseGeoCode
operation.
| |||||||||||
Returns the 20 most recent statuses, including retweets, posted by the
authenticating user and that user's friends.
| |||||||||||
Returns the 20 most recent mentions (status containing @username) for the
authenticating user.
| |||||||||||
Returns the 20 most recent statuses from non-protected users who have set a
custom user icon.
| |||||||||||
Show user objects of up to 100 members who retweeted the status.
| |||||||||||
Show user ids of up to 100 users who retweeted the status represented by id
This method calls http://api.twitter.com/1/statuses/:id/retweeted_by/ids.format | |||||||||||
Returns the 20 most recent retweets posted by the authenticating user.
| |||||||||||
Returns the 20 most recent retweets posted by the specified user.
| |||||||||||
Returns the 20 most recent retweets posted by the specified user.
| |||||||||||
Returns the 20 most recent retweets posted by the authenticating user's
friends.
| |||||||||||
Returns the 20 most recent retweets posted by users the specified user
follows.
| |||||||||||
Returns the 20 most recent retweets posted by users the specified user
follows.
| |||||||||||
Returns up to 100 of the first retweets of a given tweet.
| |||||||||||
Returns the 20 most recent tweets of the authenticated user that have been
retweeted by others.
| |||||||||||
Returns the top ten topics that are currently trending on Twitter.
| |||||||||||
Returns the 20 most recent statuses posted from the authenticating user.
| |||||||||||
Returns the 20 most recent statuses posted from the authenticating user.
| |||||||||||
Returns the 20 most recent statuses posted from the authenticating user.
| |||||||||||
Returns the top 30 trending topics for each day in a given week.
| |||||||||||
Start the OAuth request authorization process.
| |||||||||||
Retweets a tweet.
| |||||||||||
Search for places (cities and neighborhoods) that can be attached to a
statuses/update.
| |||||||||||
Returns tweets that match a specified query.
| |||||||||||
Search for places that can be attached to a statuses/update.
| |||||||||||
Set the OAuth verifier after it has been retrieved via requestAuthorization.
| |||||||||||
Returns a single status, specified by the id parameter below.
| |||||||||||
Answers user information for the authenticated user
| |||||||||||
Updates the authenticating user's status.
| |||||||||||
| Message Sources | |||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
Asynchronously retrieves public statuses that match one or more filter predicates.
| |||||||||||
Asynchronously retrieves all public statuses.
| |||||||||||
Asynchronously retrieves all statuses containing 'http:' and 'https:'.
| |||||||||||
Asynchronously retrieves a random sample of all public statuses.
| |||||||||||
Asynchronously retrieves statutes for a set of supplied user's ids.
| |||||||||||
Retrieves the following user updates notifications:
- New Statuses - Block/Unblock events - Follow events - User profile updates - Retweets - List creation/deletion - List member addition/remotion - List subscription/unsubscription - List updates - Profile updates Such notifications are represented as org.mule.twitter.UserEvent objects Only one Twitter stream can be consumed using the same credentials. | |||||||||||
To use the this module within a flow the namespace to the module must be included. The resulting flow will look similar to the following:
<mule xmlns="http://www.mulesoft.org/schema/mule/core"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:twitter="http://repository.mulesoft.org/releases/org/mule/modules/mule-module-twitter"
xsi:schemaLocation="
http://www.mulesoft.org/schema/mule/core
http://www.mulesoft.org/schema/mule/core/current/mule.xsd
http://repository.mulesoft.org/releases/org/mule/modules/mule-module-twitter
http://repository.mulesoft.org/releases/org/mule/modules/mule-module-twitter/2.3/mule-twitter.xsd">
<!-- here goes your flows and configuration elements -->
</mule>
This module is configured using the config element. This element must be placed outside of your flows and at the root of your Mule application. You can create as many configurations as you deem necesary as long as each carries its own name.
Each message processor, message source or transformer carries a config-ref attribute that allows the invoker to specify which configuration to use.
| Attributes | |||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
| Type | Name | Default Value | Description | Optional. Give a name to this configuration so it can be later referenced. | |||||||
| Optional. | |||||||||||
| Optional. | |||||||||||
| true | Optional. | ||||||||||
Creates a new place at the given latitude and longitude.
<create-place
token="#[header:token]"
containedWithin="#[header:containedWithin]"
name="#[header:placeName]"
latitude="#[header:latitude]"
longitude="#[header:longitude]"
streetAddress="[header:address]"/>
| Optional. Specify which configuration to use. | ||
| The name a place is known as. |
||
| The place_id within which the new place can be found.
Try and be as close as possible with the containing place. For
example, for a room in a building, set the contained_within as the
building place_id. |
||
| The token found in the response from geo/similar_places. |
||
| The latitude the place is located at. |
||
| The longitude the place is located at. |
||
| Optional. optional: This parameter searches for places which have
this given street address. There are other well-known, and
application specific attributes available. Custom attributes are
also permitted. Learn more about Place Attributes. |
| TwitterException |
|---|
Destroys the status specified by the required ID parameter.
Usage note: The authenticating user must be the author of the specified
status.
This method calls http://api.twitter.com/1/statuses/destroy
| Optional. Specify which configuration to use. | ||
| The ID of the status to destroy. |
| TwitterException | when Twitter service or network is unavailable |
|---|
Returns the current top 10 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.
<get-current-trends excludeHashtags="true" />
| Optional. Specify which configuration to use. | ||
| Optional. whether all hashtags shoudl be removed from the trends list. |
| TwitterException |
|---|
Returns the top 20 trending topics for each hour in a given day.
<get-daily-trends />
| Optional. Specify which configuration to use. | ||
| Optional. starting date of daily trends. If no date is specified, current
date is used |
||
| Optional. whether hashtags should be excluded |
| TwitterException |
|---|
Find out more details of a place that was returned from the reverseGeoCode
operation.
<get-geo-details id="#[header:geocodeId]"/>
| Optional. Specify which configuration to use. | ||
| The ID of the location to query about. |
| TwitterException |
|---|
Returns the 20 most recent statuses, including retweets, posted by the
authenticating user and that user's friends. This is the equivalent of
/timeline/home on the Web.
Usage note: This home_timeline call is identical to statuses/friends_timeline,
except that home_timeline also contains retweets, while
statuses/friends_timeline does not for backwards compatibility reasons. In a
future version of the API, statuses/friends_timeline will be deprected and
replaced by home_timeline.
This method calls http://api.twitter.com/1/statuses/home_timeline
| Optional. Specify which configuration to use. | ||
| 1 | controls pagination. Supports since_id, max_id, count and page
parameters. |
|
| 100 | ||
| -1 |
| TwitterException | when Twitter service or network is unavailable |
|---|
Returns the 20 most recent mentions (status containing @username) for the
authenticating user.
This method calls http://api.twitter.com/1/statuses/mentions
| Optional. Specify which configuration to use. | ||
| 1 | ||
| 100 | ||
| -1 |
| TwitterException | when Twitter service or network is unavailable |
|---|
Returns the 20 most recent statuses from non-protected users who have set a
custom user icon. The public timeline is cached for 60 seconds and requesting
it more often than that is unproductive and a waste of resources.
This method calls http://api.twitter.com/1/statuses/public_timeline
| Optional. Specify which configuration to use. |
| TwitterException | when Twitter service or network is
unavailable |
|---|
Show user objects of up to 100 members who retweeted the status.
This method calls http://api.twitter.com/1/statuses/:id/retweeted_by
| Optional. Specify which configuration to use. | ||
| The ID of the status you want to get retweeters of |
||
| 1 | ||
| 100 | ||
| -1 |
| TwitterException | when Twitter service or network is unavailable |
|---|
Show user ids of up to 100 users who retweeted the status represented by id
This method calls
http://api.twitter.com/1/statuses/:id/retweeted_by/ids.format
| Optional. Specify which configuration to use. | ||
| The ID of the status you want to get retweeters of |
||
| 1 | ||
| 100 | ||
| -1 |
| TwitterException | when Twitter service or network is unavailable |
|---|
Returns the 20 most recent retweets posted by the authenticating user.
This method calls http://api.twitter.com/1/statuses/retweeted_by_me
| Optional. Specify which configuration to use. | ||
| 1 | ||
| 100 | ||
| -1 |
| TwitterException | when Twitter service or network is unavailable |
|---|
Returns the 20 most recent retweets posted by the specified user. This method
is identical to statuses/retweeted_by_me except you can choose the user to
view.
This method has not been finalized and the interface is subject to change in
incompatible ways.
This method calls http://api.twitter.com/1/statuses/retweeted_by_user
| Optional. Specify which configuration to use. | ||
| the user to view |
||
| 1 | ||
| 100 | ||
| -1 |
| TwitterException | when Twitter service or network is unavailable |
|---|
Returns the 20 most recent retweets posted by the specified user. This method
is identical to statuses/retweeted_by_me except you can choose the user to
view.
This method has not been finalized and the interface is subject to change in
incompatible ways.
This method calls http://api.twitter.com/1/statuses/retweeted_by_user
| Optional. Specify which configuration to use. | ||
| the user to view |
||
| 1 | ||
| 100 | ||
| -1 |
| TwitterException | when Twitter service or network is unavailable |
|---|
Returns the 20 most recent retweets posted by the authenticating user's
friends.
This method calls http://api.twitter.com/1/statuses/retweeted_to_me
| Optional. Specify which configuration to use. | ||
| 1 | ||
| 100 | ||
| -1 |
| TwitterException | when Twitter service or network is unavailable |
|---|
Returns the 20 most recent retweets posted by users the specified user
follows. This method is identical to statuses/retweeted_to_me except you can
choose the user to view.
This method has not been finalized and the interface is subject to change in
incompatible ways.
This method calls http://api.twitter.com/1/statuses/retweeted_to_user
| Optional. Specify which configuration to use. | ||
| the user to view |
||
| 1 | ||
| 100 | ||
| -1 |
| TwitterException | when Twitter service or network is unavailable |
|---|
Returns the 20 most recent retweets posted by users the specified user
follows. This method is identical to statuses/retweeted_to_me except you can
choose the user to view.
This method has not been finalized and the interface is subject to change in
incompatible ways.
This method calls http://api.twitter.com/1/statuses/retweeted_to_user
| Optional. Specify which configuration to use. | ||
| the user to view |
||
| 1 | ||
| 100 | ||
| -1 |
| TwitterException | when Twitter service or network is unavailable |
|---|
Returns up to 100 of the first retweets of a given tweet.
This method calls http://api.twitter.com/1/statuses/retweets
| Optional. Specify which configuration to use. | ||
| The numerical ID of the tweet you want the retweets of. |
| TwitterException | when Twitter service or network is unavailable |
|---|
Returns the 20 most recent tweets of the authenticated user that have been
retweeted by others.
This method calls http://api.twitter.com/1/statuses/retweets_of_me
| Optional. Specify which configuration to use. | ||
| 1 | ||
| 100 | ||
| -1 |
| TwitterException | when Twitter service or network is unavailable |
|---|
Returns the top ten topics that are currently trending on Twitter. The
response includes the time of the request, the name of each trend, and the url
to the Twitter Search results page for that topic.
<get-trends/>
| Optional. Specify which configuration to use. |
| TwitterException |
|---|
Returns the 20 most recent statuses posted from the authenticating user. It's
also possible to request another user's timeline via the id parameter.
This is the equivalent of the Web / page for your own user, or the profile
page for a third party.
For backwards compatibility reasons, retweets are stripped out of the
user_timeline when calling in XML or JSON (they appear with 'RT' in RSS and
Atom). If you'd like them included, you can merge them in from statuses
retweeted_by_me.
This method calls http://api.twitter.com/1/statuses/user_timeline.json
| Optional. Specify which configuration to use. | ||
| 1 | ||
| 100 | ||
| -1 |
| TwitterException | when Twitter service or network is unavailable |
|---|
Returns the 20 most recent statuses posted from the authenticating user. It's
also possible to request another user's timeline via the id parameter.
This is the equivalent of the Web / page for your own user, or the profile
page for a third party.
For backwards compatibility reasons, retweets are stripped out of the
user_timeline when calling in XML or JSON (they appear with 'RT' in RSS and
Atom). If you'd like them included, you can merge them in from statuses
retweeted_by_me.
This method calls http://api.twitter.com/1/statuses/user_timeline.json
| Optional. Specify which configuration to use. | ||
| specifies the screen name of the user for whom to return the
user_timeline |
||
| 1 | ||
| 100 | ||
| -1 |
| TwitterException | when Twitter service or network is unavailable |
|---|
Returns the 20 most recent statuses posted from the authenticating user. It's
also possible to request another user's timeline via the id parameter.
This is the equivalent of the Web / page for your own user, or the profile
page for a third party.
For backwards compatibility reasons, retweets are stripped out of the
user_timeline when calling in XML or JSON (they appear with 'RT' in RSS and
Atom). If you'd like them included, you can merge them in from statuses
retweeted_by_me.
This method calls http://api.twitter.com/1/statuses/user_timeline.json
| Optional. Specify which configuration to use. | ||
| specifies the ID of the user for whom to return the
user_timeline |
||
| 1 | ||
| 100 | ||
| -1 |
| TwitterException | when Twitter service or network is unavailable |
|---|
Returns the top 30 trending topics for each day in a given week.
<get-weekly-trends/>
| Optional. Specify which configuration to use. | ||
| Optional. starting date of daily trends. If no date is specified, current
date is used |
||
| Optional. if all hashtags should be removed from the trends list. |
| TwitterException |
|---|
Start the OAuth request authorization process.
| Optional. Specify which configuration to use. | ||
| Optional. |
| TwitterException |
|---|
Retweets a tweet. Returns the original tweet with retweet details embedded.
This method calls http://api.twitter.com/1/statuses/retweet
| Optional. Specify which configuration to use. | ||
| The ID of the status to retweet. |
| TwitterException | when Twitter service or network is unavailable |
|---|
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.
<reverse-geo-code ip="#[header:ip]" />
| Optional. Specify which configuration to use. | ||
| Optional. latitude coordinate. Mandatory if ip is not specified |
||
| Optional. longitude coordinate. |
||
| Optional. the ip. Mandatory if coordinates are not specified |
| TwitterException |
|---|
Returns tweets that match a specified query.
This method calls http://search.twitter.com/search.json
@return
| Optional. Specify which configuration to use. | ||
| The search query. |
| TwitterException |
|---|
Search for places that can be attached to a statuses/update. Given a latitude
and a longitude pair, or and IP address, this request will return a list of
all the valid places that can be used as the place_id when updating a status.
<search-places latitude="#[header:latitude]" longitude="#[header:longitude]" />
| Optional. Specify which configuration to use. | ||
| Optional. latitude coordinate. Mandatory if ip is not specified |
||
| Optional. longitude coordinate. |
||
| Optional. the ip. Mandatory if coordinates are not specified |
| TwitterException |
|---|
Set the OAuth verifier after it has been retrieved via requestAuthorization.
The resulting access tokens will be logged to the INFO level so the user can
reuse them as part of the configuration in the future if desired.
| Optional. Specify which configuration to use. | ||
| The OAuth verifier code from Twitter. |
| TwitterException |
|---|
Returns a single status, specified by the id parameter below. The status's
author will be returned inline.
This method calls http://api.twitter.com/1/statuses/show
| Optional. Specify which configuration to use. | ||
| the numerical ID of the status you're trying to retrieve |
| TwitterException | when Twitter service or network is
unavailable |
|---|
Answers user information for the authenticated user
| Optional. Specify which configuration to use. |
| TwitterException |
|---|
Updates the authenticating user's status. A status update with text identical
to the authenticating user's text identical to the authenticating user's
current status will be ignored to prevent duplicates.
This method calls http://api.twitter.com/1/statuses/update
| Optional. Specify which configuration to use. | ||
| the text of your status update |
||
| Optional. | ||
| Optional. |
| TwitterException | when Twitter service or network is unavailable |
|---|
Asynchronously retrieves public statuses that match one or more filter predicates.
At least a keyword or userId must be specified. Multiple parameters may be
specified.
Placing long parameters in the URL may cause the request to be rejected for excessive URL length.
The default access level allows up to 200 track keywords and 400 follow userids.
Only one Twitter stream can be consumed using the same credentials. As a consequence,
only one twitter stream can be consumed per connector instance.
<filtered-stream count="5">
<keywords>
<keyword>enterprise</keyword>
<keyword>integration</keyword>
</keywords>
</filtered-stream>
| Optional. Specify which configuration to use. | ||
| Optional. the number of previous statuses to stream before transitioning to the live stream. |
||
| Optional. the user ids to follow |
||
| Optional. the keywords to track |
||
Asynchronously retrieves all public statuses. This stream is not generally
available - it requires special permissions and its usage is discouraged by
Twitter
Only one Twitter stream can be consumed using the same credentials. As a consequence,
only one twitter stream can be consumed per connector instance.
| Optional. Specify which configuration to use. | ||
Asynchronously retrieves all statuses containing 'http:' and 'https:'. Like
Firehorse, its is not a generally available stream
Only one Twitter stream can be consumed using the same credentials. As a consequence,
only one twitter stream can be consumed per connector instance.
| Optional. Specify which configuration to use. | ||
Asynchronously retrieves a random sample of all public statuses. The sample
size and quality varies depending on the account permissions
The default access level provides a small proportion of the Firehose. The "Gardenhose"
access level provides a proportion more suitable for data mining
and research applications that desire a larger proportion to be
statistically significant sample.
Only one Twitter stream can be consumed using the same credentials. As a consequence,
only one twitter stream can be consumed per connector instance.
<sample-stream/>
| Optional. Specify which configuration to use. | ||
Asynchronously retrieves statutes for a set of supplied user's ids.
Site Streams are a beta service, so refer always to latest twitter documentation about them.
Only one Twitter stream can be consumed using the same credentials. As a consequence,
only one twitter stream can be consumed per connector instance.
| Optional. Specify which configuration to use. | ||
| ids of users to include in the stream |
||
| Optional. withFollowings whether to receive status updates from people following |
||
Retrieves the following user updates notifications:
- New Statuses
- Block/Unblock events
- Follow events
- User profile updates
- Retweets
- List creation/deletion
- List member addition/remotion
- List subscription/unsubscription
- List updates
- Profile updates
Such notifications are represented as org.mule.twitter.UserEvent objects
Only one Twitter stream can be consumed using the same credentials. As a consequence,
only one twitter stream can be consumed per connector instance.
<user-stream>
<keywords>
<keyword>enterprise</keyword>
<keyword>integration</keyword>
</keywords>
</user-stream>
| Optional. Specify which configuration to use. | ||
| the keywords to track for new statuses |
||