The Photobucket API is an application programming interface that enables software developers to give Photobucket users access to their online images and videos from environments outside of Photobucket, including other Web sites, Web applications, desktop applications, browser plug-ins, and devices that go beyond the desktop, such as mobile phones, home-entertainment systems, digital photo frames and digital cameras.
You should consider using the API for your application if:
If the API does not suit your application requirements, consider using the Photobucket Media Plug-in and/or the Photobucket RSS feeds. These options may be a simpler solution for your project.
Yes, it is completely free to use. Note that commercial developers are required to submit their business models in writing and receive approval from Photobucket. See Commercial vs. Non-Commercial.
Before you can use the API, you must:
Information about the requirements listed in steps 3 to 6 is provided in the API Documentation.
The API is accessed via HTTP commands, as outlined in the documentation, and produces responses in your specified format (e.g. XML or JSON). Access is controlled via OAuth authentication.
The API allows you to programmatically access much of the functionality of the Photobucket site. This includes Search, Uploading, User Albums, and Media Tagging and Titling. See Methods in the API Documentation.
The API can be accessed from anywhere on the Internet as long as you can implement OAuth and send and receive responses. This includes Flash, JavaScript, mobile applications, and other devices.
When you sign up as a Developer to use the API, you can access the Developer forum and the help documentation. If you are a partner, you can also access the Partner Developer forum, and you should review your partner agreement for any specific support you are eligible for. Photobucket makes the best effort to help whenever possible, but support is not guaranteed.
When you become a Developer on the Photobucket site, you have access to the developer forum . Updates to the API and documentation are provided there.
Photobucket will update the API as needed to support new functionality or fix defects. Some of these fixes will be based on developer input.
Applications and devices submitted by partners, that support the API are listed at Photobucket's Application Gallery. The Application Gallery also lists the applications currently available for download.
You do not have to submit your application to Photobucket unless you want it considered for inclusion in the Application Gallery.
No. The API is meant for augmenting the Photobucket service, not replacing it.
If you log into your Photobucket account from another site, you must enter your Photobucket username/password and grant permission to the application on the other site to access your media.
Developers are required to agree to a special Terms of Service when they access the API and begin work. The Terms of Service do not allow Developers to store user login information, other than for the amount of time that it takes to perform requests for a logged in user. In addition, those Developers are bound by the Photobucket end-user Terms of Service for any application they create.
Contact Photobucket at api@photobucket.com for questions about using the API in a commercial situation.
Commercial use is defined as any uses of the API for any services that a Developer has created to make money. For example, subscription services, premium services, photo products, and desktop products.
Non-commercial use is defined as any uses of the API for any services that a developer has created that do not make money. For example, you build a widget for yourself and your friends so you can view updated images in your album that posts to your MySpace page. You do not intend to sell advertising, and you are using the widget to share and post images with your friends.
Please read the Developer Terms of Use for specific definitions of what you can and cannot do with a non-commercial key.
For developers with an approved business plan for their application, Photobucket provides a commercial API option with unlimited traffic and bandwidth. Sign up for the non-commercial key first, and then email us at api@photobucket.com.
You must agree to the Developer Terms of Use and sign up for an API key before your Photobucket User account becomes a Photobucket Developer account, too.
You cannot create a Developer account unless you have a Photobucket User account.
Your Photobucket User account and login information is the same as your Developer login. After you log into Photobucket, you have access to all the areas available to your account, which includes signing up for Developer access.
Your Photobucket User account (with your albums and media) is the same account as your Developer account. If you are logged in, you have access to all areas available to your account.
You can submit your application to Photobucket to be considered for the Application Gallery.
Photobucket may also ask certain applications if they wish to be included in the gallery.
The Application of the Day, which displays in the Photobucket Gallery, showcases specific applications that use the Photobucket API. The Application of the Day is selected by Photobucket.
An Open Social Application is an application that implements the Open Social specification which can run on any Open Social supporting site, like Orkut, Linked-in, Bebo, or MySpace in a widget or as a feature.
You can find details about Open Social at http://code.google.com/apis/opensocial/.
No. You must submit your application to the Open Social site yourself. Partners, please contact Photobucket if you require assistance.
Photobucket does not currently implement the Open Social containers or API. Photobucket services can be used to support Open Social applications on other platforms, such as Myspace or Orkut.
The Photobucket RSS feeds documentation explains how to use the Photobucket RSS feeds. Note that Photobucket RSS feeds only contain public media, they are ordered by upload date, and they are only published every hour.
The Photobucket Media Plug-in documentation explains how to use the Media Plug-in.
Photobucket separates users into ‘silos’; each one accessible by a specific number. If you check the User URLs response for a given user, you can see which sub-domains that user can be accessed by. Photobucket also provides this information in the token access responses. To access a user’s content, you must interact with that specific silo, and Photobucket provides the redirects as a convenience.
Some HTTP clients cannot handle these redirects, and Photobucket ultimately prefers that you use the information given, rather than relying on the redirects. The silo information for a user can safely be cached for a time, per user, to save calls. The silo hostnames can present a problem with OAuth signing, which requires the entire hostname and URL in the signature. For this reason, we require ALL requests, regardless of the silo being accessed, to use "http://api.photobucket.com" as the beginning of the URL being hashed in the OAuth signature process to help work around the issue of redirects and hostnames.
The OAuth basestring will look like certain parts are double encoded (mainly, the parameters to the request). This is normal, and you should not see characters other than ALPHA / DIGIT / "-" / "." / "_" / "~", and obviously the %XX characters in the encoded fields, separated by unencoded "&"
Parts:
Using a pre-built library from OAuth.net can do this for you.