Blipfoto API

Breaking changes - legacy APIs will be disabled 6th January, 2014

Please note - the v1 and v2 APIs will be permanently disabled on Monday the 6th of January, 2014. If your app uses these APIs, you should migrate to v3 before this date to ensure your app continues to function correctly.

Migrating your app to v3 will require some fundamental changes, including updating resource URLs and handling the new authentication flow. You can read more about migration at the new developer site:

https://developer.blipfoto.com/docs/v3/migration

For further help with the v3 API, ask a question on the API forum or get in touch.

Test accounts

Instead of creating a sandbox for application testing, we can provide you with a test account. Entries added to this account are not displayed to visitors or other members, allowing you to upload entries or post comments to the test account without impacting the public website. Just drop us a line and we'll set one up for you.

How do test accounts work?

A test account is a basic Blipfoto account. You can sign-in to the account, publish entries, and edit your profile as normal. However, other members cannot see your journal listings on the homepage or in search results.

Returning test data via the API

API requests do not return listings from test accounts by default. To prompt the API to include entries from your test account, see the get/view and get/search resources.

Publishing test data via the API

Wherever possible, you should authenticate API calls through your test account. You can view updates to the test journal from your standard account on the Blipfoto website.