500px API provides programmatic access to 500px functionality and content. Version 1 of the API is limited to the essentials of the website's functionality: viewing feature streams, photo information and comments, as well as user profiles.
The API is REST API and uses OAuth 1.0a for user authentication purposes. Currently, return format for all endpoints is JSON.
You can try our API in console (http://bitly.com/api500px)
See status.500px.com for API status updates, outages, and scheduled maintenance.
- Try the API console
- See if the concepts used by the API are familiar to you
- Familiarize yourself with API functionality
- Read the 500px API Terms of Use
- Register your application and get OAuth consumer key and secret
- Hack away
- 2014-03-27 Deprecated photo object's image_url key.
GET
photosGET
photos/searchGET
photos/:idGET
photos/:id/commentsGET
photos/:id/favoritesGET
photos/:id/votesPUT
photos/:idPOST
photosPOST
photos/uploadPOST
photos/:id/votePOST
photos/:id/tagsPOST
photos/:id/favoritePOST
photos/:id/commentsPOST
photos/:id/reportDELETE
photos/:idDELETE
photos/:id/tagsDELETE
photos/:id/favorite
GET
usersGET
users/showGET
users/:id/friendsGET
users/:id/followersGET
users/searchPOST
users/:id/friendsDELETE
users/:id/friends
GET
blogsGET
blogs/:idGET
blogs/:id/commentsPOST
blogs/:id/commentsPOST
blogsPUT
blogs/:idDELETE
blogs/:id
Got rust on your skills? No worries. Here are the docs you might need to get started:
- HTTPS protocol
- REST software pattern
- Authentication with OAuth (or the official Beginner’s Guide)
- Data serialization with JSON (or see a quick tutorial)
The API is only available to authenticated clients. Clients should authenticate users using OAuth. Once authenticated, you need to request a resource from one of the endpoints using HTTPS. Generally, reading any data is done through a request with GET method. If you want our server to create, update or delete a given resource, POST or PUT methods are required.
500px API currently returns data in JSON format.
Applications must identify themselves to access any resource. If your application only needs read-only access and does not authenticate the user, consumer_key containing a valid Consumer Key parameter should be specified in the query string. Otherwise, OAuth or upload key authentication takes care of identifying the application as well as the user accessing the API.
There is a rate limit of 1,000,000 API requests per month per account. We will contact you and if required disable your application if we find that your application is exceeding this limit or interfering with our system's stability.This revised rate limit will come into effect May 1, 2014.