Flickr Photos Of API
The photos one person appears in, rather than the photos they uploaded.
GET /v1/flickr/users/{userId}/photos-of1 credit Failed requests are free
About this endpoint
GET /v1/flickr/users/{userId}/photos-of returns a page of data.photos: the photos the person is tagged in. Each row is a full photo record with the photographer, sizes, counts, dates, tags and geo. The route accepts an NSID or a path alias.
This answers a different question from the photostream: the photostream is what the person uploaded, this list is where they appear. Paging uses limit, page and page.nextCursor, with at most 100 rows a page. A walk can repeat a row when several photos share a posted time; de-duplicate by id when you need an exact set. An unknown person returns not_found.
Flickr Photos Of API FAQ
How is this different from the photostream?
The photostream is the person’s own uploads. Photos-of lists photos by other photographers that tag the person.
What order are the photos in?
The order the public tagged-photos list gives them. Use the photostream for a strict upload order.
How much does a photos-of page cost?
Pricing is documented on the operation in the API registry (shown on this page). Confirm on every response with meta.creditsCharged: that field is the billing source of truth. Each paginated page is a separate billed request.
Why can the list be empty for a real person?
The person may have no public tagged photos. lookupStatus is found and photos is empty in that case.
Other Flickr endpoints
- PhotoGET /v1/flickr/photos/{photoId}
- CommentsGET /v1/flickr/photos/{photoId}/comments
- EXIFGET /v1/flickr/photos/{photoId}/exif
- Favourited byGET /v1/flickr/photos/{photoId}/favorites
- ContextsGET /v1/flickr/photos/{photoId}/contexts
- UserGET /v1/flickr/users/{userId}
- PhotostreamGET /v1/flickr/users/{userId}/photos
- AlbumsGET /v1/flickr/users/{userId}/albums