The SuperTweet.net Twitter SupertweetAPI Proxy implements the Twitter REST API v1.1, as described at Twitter API Documentation. Simply substitute the hostname api.supertweet.net instead of api.twitter.com and use your SuperTweet.net Basic Auth credentials instead of your actual twitter username/password.
For example, to send a tweet, use the /1.1/statuses/update.json such as:
curl -u user:password -d "status=playing with cURL and the SuperTweet.net API" http://api.supertweet.net/1.1/statuses/update.json
curl -u user:password http://api.supertweet.net/1.1/statuses/home_timeline.json
curl -u user:password http://api.supertweet.net/1.1/ACLU/aclu-affiliates/members.json
curl -u user:password -d "text=There's no place like 127.0.0.1&user=user_2" http://api.supertweet.net/1.1/direct_messages/new.json
curl -u user:password -d "" http://api.supertweet.net/1.1/blocks/create/mrblog.json
The api.supertweet.net API endpoints should pass the exact same data of the corresponding direct Twitter API, including any error codes and error message, in the exact same JSON format.
Upon executing a proxied Twitter API request, whether successful or not, the SuperTweet.net API returns the response status code and any error messages received from the Twitter API. This means that even if the SuperTweet.net proxy request succeeded, in the sense that the Twitter API was invoked, an error status code and corresponding error message may still be returned, as a result of an error on the Twitter side. A special header is provided in the response, set by the SuperTweet.net API proxy, as follows:
If this header exists in the response, then the status code and error message represent those returned by the Twitter API. If this special header is not present in the response, then the status code and error message are those of the SuperTweet.net API service itself (not from the Twitter API).
The SuperTweet.net API returns the response status code received from the Twitter API, generally defined as.
The SuperTweet.net API returns error messages as appropriate, either proxied as is from the Twitter API (when the X-TwitterAPI-Status header is present) or generated directly by the SuperTweet.net API proxy service. When the Twitter API returns error messages, it generally does so in your requested format. Occasionally it will return an HTML formatted error message body for a JSON or XML request (usually in the case of 5xx errors).