We currently fully support XML format responses.
Some additional parameters are required for all Fanvibe API calls.
|For bevity, example API calls do not include these parameters.|
Making calls to the API will require you to set a unique user-agent. Generic user-agents may be blocked in certain occasions, and we also will use user-agents for rate limiting and other analytic purposes. All API calls should include in the User-Agent header “Fanvibe-API”
A user-agent example "NBA/GameTime Fanvibe-API (android)"
Non-OAuth requests are usually any call that does not require a POST, PUT, or DESTROY. Each call needs to include a consumer_key parameter, which acts like the deprecated api_key parameter. This consumer_key is the same one used when you register your application on Fanvibe to connect with OAuth.
$ curl http://fanvibe.com/api/awards/first.xml?consumer_key=wO4odZp3aq9xzQRAb21A
All user specific requests, such as any POST, PUT, or DESTROY, will require an OAuth authenticated call. See our OAuth docs for more information.
NOTE: For information about these OAuth parameters, see the OAuth Core docs