Unsplash API Guidelines
Thanks for your interest in the Unsplash API.
To save time and increase your chances of having your application approved, please make sure that your application submission meets the guidelines.
If your submission does not clearly meet all of the guidelines, it will likely be rejected for a rate limit increase until you provide clear examples of all of the guidelines being met.
- All API uses must use the hotlinked image URLs returned by the API under the
photo.urlsproperties. More info & examples →
- When your application performs something similar to a download (like when a user chooses the image to include in a blog post, set as a header, etc.), you must send a request to the download endpoint returned under the
photo.links.download_locationproperty. More info & examples →
- When displaying a photo from Unsplash, your application must attribute Unsplash, the Unsplash photographer, and contain a link back to their Unsplash profile. All links back to Unsplash should use
utmparameters in the
?utm_source=your_app_name&utm_medium=referral. More info & examples →
- You cannot use the Unsplash name directly in your application name and you cannot use the Unsplash logo as an app icon.
- You cannot use the API to sell unaltered Unsplash photos directly or indirectly (prints, on products, etc.)
- You cannot replicate the core user experience of Unsplash. More info & examples →
- The API is to be used for non-automated, high-quality, and authentic experiences. More info & examples →
- Do not abuse the APIs. Too many requests too quickly will get your access turned off.
We recommend taking a look at each of the accompanying articles as they provide visual and code examples. If after reading those you have any questions, feel free to reach out to us.
Happy building! 👏