Difference between revisions of "SoFurry REST APIs"
(→Overview) |
|||
| (One intermediate revision by the same user not shown) | |||
| Line 14: | Line 14: | ||
* [[OAuth 2.0]] | * [[OAuth 2.0]] | ||
| + | * [[Tutorial: Connecting to the SoFurry API]] | ||
* [[:Category:REST API calls|SoFurry API calls]] | * [[:Category:REST API calls|SoFurry API calls]] | ||
* [[Uploading media]] | * [[Uploading media]] | ||
| Line 24: | Line 25: | ||
The SoFurry API requires all applications to authenticate all of their request with [[OAuth 2.0]]. This allows us to prevent abusive behavior and it also helps us improving the API. | The SoFurry API requires all applications to authenticate all of their request with [[OAuth 2.0]]. This allows us to prevent abusive behavior and it also helps us improving the API. | ||
| + | |||
| + | For more details regarding the API authentication, look [[OAuth 2.0|here]]. | ||
[[Category:Development]] | [[Category:Development]] | ||
Latest revision as of 10:12, 6 March 2016
|
SoFurry's REST APIs provide programmatic access to read/write data from/to the website. The REST API identifies SoFurry applications and users using OAuth 2.0. Responses are available in JSON, XML or PHP.
Overview
Below are the docs that will help you get going with the REST API with as much ease as possible
Latest updates
A new API version is currently in development which will require every application to use OAuth and authenticate before accessing any of the site's functions. Additionally, the error responses will be standardized, providing more details and making it easier for developers to handle them correctly in applications.
Endpoint authentication
The SoFurry API requires all applications to authenticate all of their request with OAuth 2.0. This allows us to prevent abusive behavior and it also helps us improving the API.
For more details regarding the API authentication, look here.
