> **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/albums-albumid>
- **Markdown (.mdx) URL:** <https://www.socialfetch.dev/platforms/flickr/albums-albumid.mdx>

---

# Flickr Album API

One album with its metadata and a page of the photos inside it.

`GET /v1/flickr/albums/{albumId}` needs an album id and a `userId`, because the album belongs to a person. It returns `data.album` (title, description, owner, counts including views and comments, sortType, primary photo URL and create/update dates) and a page of `data.photos` with the same full photo record as a photo lookup.

When the person is given as an alias, it is resolved to an NSID first. An unknown album or owner returns `lookupStatus: not_found` and a null album. If the extra album metadata is unavailable, the photos still come back and the answer is marked degraded.

## Request

- **Endpoint:** `GET /v1/flickr/albums/{albumId}`
- **Credits:** 1 credit
Failed requests are free
- **Input:** by album id and user
- **Full reference:** [docs](https://www.socialfetch.dev/docs/api/v1/flickr/albums/albumid/get)
- **Platform page:** [/platforms/flickr](https://www.socialfetch.dev/platforms/flickr)

## FAQ

### Why do I need a user id with the album id?

Albums are addressed by owner and album id together. Pass an NSID or a path alias in the userId parameter.

### Does it return every photo in the album?

It returns one page, up to 100 photos. Follow page.nextCursor while page.hasMore is true to walk the album.

### 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 the album dates and view count real?

Yes. On the first page the route also reads the album's own metadata, so createdAt, updatedAt, views, comments and primaryPhotoUrl are filled. Unavailable metadata leaves them null or from the photo list and marks the answer degraded.