Download the PHP package zendframework/zendservice-twitter without Composer
On this page you can find all versions of the php package zendframework/zendservice-twitter. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.
Download zendframework/zendservice-twitter
More information about zendframework/zendservice-twitter
Files in zendframework/zendservice-twitter
Package zendservice-twitter
Short Description OOP wrapper for the Twitter web service
License BSD-3-Clause
Informations about the package zendservice-twitter
zendservice-twitter
Repository abandoned 2019-12-31
This repository has moved to laminas/laminas-twitter.
Provides an object oriented PHP wrapper for the Twitter API.
Installation
Run the following to install this library:
Usage
Instantiate the Twitter
class by providing your Twitter consumer key and
secret, as well as the access token and secret:
Once you have done that, you may start making calls to the API. This can be done in one of three ways:
- Using direct method calls on the
Twitter
class. A full list is provided below. - Using the "proxy" functionality. In these cases, you will provide the first
path element of the API, and then call a method on it:
$twitter->statuses->update($message)
. - Using the
get()
orpost()
methods.
Available methods
accountVerifyCredentials() : Response
applicationRateLimitStatus() : Response
blocksCreate($id) : Response
blocksDestroy($id) : Response
blocksIds(int $cursor = -1) : Response
blocksList(int $cursor = -1) : Response
directMessagesDestroy($id) : Response
directMessagesMessages(array $options = []) : Response
directMessagesNew($user, string $text, array $extraParams = []) : Response
directMessagesEventsNew($user, string $text, array $extraParams = []) : Response
directMessagesSent(array $options = []) : Response
favoritesCreate($id) : Response
favoritesDestroy($id) : Response
favoritesList(array $options = []) : Response
followersIds($id, array $params = []) : Response
friendsIds($id, array $params = []) : Response
friendshipsCreate($id, array $params = []) : Response
friendshipsLookup($id, array $params = []) : Response
friendshipsDestroy($id) : Response
listsMembers($listIdOrSlug, array $params = []) : Response
listsMemberships($id, array $params = []) : Response
listsSubscribers($id, array $params = []) : Response
searchTweets(string $query, array $options = []) : Response
statusesDestroy($id) : Response
statusesHomeTimeline(array $options = []) : Response
statusesMentionsTimeline(array $options = []) : Response
statusesSample() : Response
statusesShow($id, array $options = []) : Response
statusesUpdate(string $status, $inReplyToStatusId = null, $extraAttributes = []) : Response
statusesUserTimeline(array $options = []) : Response
usersLookup($id, array $params = []) : Response
usersSearch(string $query, array $options = []) : Response
usersShow($id) : Response
Proxy Properties
The following proxy properties are allowed:
- account
- application
- blocks
- directmessages
- favorites
- followers
- friends
- friendships
- lists
- search
- statuses
- users
In each case, you can identify available methods for the proxy by comparing the
proxy name to the above list of methods. As an example, the users
proxy allows
the following:
Direct access
The Twitter API has dozens of endpoints, some more popular and/or useful than others. As such, we are only providing a subset of what is available.
However, we allow you to access any endpoint via either the get()
or post()
methods, which have the following signatures:
In each case, the $path
is the API endpoint as detailed in the Twitter API
documentation, minus any .json
suffix, and the method name corresponds to
whether the request happens via HTTP GET or POST.
For HTTP GET requests, the $query
argument provides any query string
parameters you want to pass for that endpoint. As an example, if you were
requesting statuses/home_timeline
, you might pass count
or since_id
.
For HTTP POST requests, the $data
argument can be one of:
- An associative array of data.
- A serializable object of data.
- A string representing the raw payload.
The data to provide will vary based on the endpoint.
Media uploads
Since version 3.0, we have supported media uploads via the classes
ZendService\Twitter\Media
, Image
, and Video
. In each case, you will
instantiate the appropriate class with the local filesystem path of the image to
upload and the media type, followed by calling upload()
with a properly
configured HTTP client. The response will contain a media_id
property, which
you can then provide via the media_ids
parameter when posting a status:
When providing media for direct messages, you must provide additional flags to the media class's constructor:
- A flag indicating it is for a direct message
- A flag indicating whether or not the uploaded media may be shared/re-used in other direct messages.
Unlike non-DM media uploads, the identifier will be in the id_str
parameter of
the returned upload instance; use that as a media_id
in your DM:
Note: direct messages only support a single attachment.
Rate limiting
As of version 3.0, we now provide introspection of Twitter's rate limit headers, allowing you to act on them:
All versions of zendservice-twitter with dependencies
zendframework/zend-feed Version ^2.7
zendframework/zend-http Version ^2.5.4
zendframework/zend-json Version ^2.6.1 || ^3.0
zendframework/zend-stdlib Version ^2.7.7 || ^3.0.1
zendframework/zend-uri Version ^2.5.2
zendframework/zendoauth Version ^2.0.3