> **For coding agents and LLMs:** This is one Social Fetch marketing page (markdown export). For API orientation start with [`/llms.txt`](https://www.socialfetch.dev/llms.txt); for auth and crawl rules use [`/agents.txt`](https://www.socialfetch.dev/agents.txt); for every operation use [`/llms-endpoints.txt`](https://www.socialfetch.dev/llms-endpoints.txt).

## This page

- **On-site (HTML):** <https://www.socialfetch.dev/platforms/flickr/users-userid-albums-list>
- **Markdown (.mdx) URL:** <https://www.socialfetch.dev/platforms/flickr/users-userid-albums-list.mdx>

---

# Flickr Albums API

A user’s albums with photo counts, covers and sort order, page by page.

`GET /v1/flickr/users/{userId}/albums` returns `data.user` and a page of `data.albums`. Each album carries `id`, `url`, `title`, `description`, `owner`, `counts` (photos, videos, publicPhotos, views and comments), `sortType`, `primaryPhotoId`, `primaryPhotoUrl`, `createdAt` and `updatedAt`.

`sortType` tells you how the owner arranged the album, for example `manual-add-to-end`. Use the album id with `GET /v1/flickr/albums/{albumId}` to read the photos inside. Paging uses `limit`, `page` and `page.nextCursor`, with at most 100 albums a page.

## Request

- **Endpoint:** `GET /v1/flickr/users/{userId}/albums`
- **Credits:** 1 credit
Failed requests are free
- **Input:** by NSID or alias
- **Full reference:** [docs](https://www.socialfetch.dev/docs/api/v1/flickr/users/userid/albums/list)
- **Platform page:** [/platforms/flickr](https://www.socialfetch.dev/platforms/flickr)

## FAQ

### How do I list the photos in one album?

Take the album id from this response and call GET /v1/flickr/albums/{albumId} with your user id. This route lists albums, not their photos.

### What is primaryPhotoUrl?

A 150 pixel cover image URL when the album record carries the photo secret. It can be null for an album without an available cover.

### How much does an album 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.

### Are create and update dates always present?

Not always. The album list carries them when the record shows them; the single album route can return null dates because its primary request does not include them.