Mastodon hub

Mastodon Collections API

An account's curated collections, with their member accounts, on servers new enough to offer them.

GET /v1/mastodon/profiles/{handle}/collections

1 credit Failed requests are free

About this endpoint

GET /v1/mastodon/profiles/{handle}/collections resolves the account and returns its curated collections. Each entry in data.collections carries id, name, description, language, hashtag, url, uri, isDiscoverable, isSensitive, itemCount, createdAt, updatedAt and an items list. Each item has id, state, accountId, createdAt and, when available, the full member account.

Collections arrived in Mastodon 4.7. Older servers and forks that do not implement the route return lookupStatus: unsupported with an empty list, not not_found. The route fills in up to 40 distinct member accounts; when those accounts are temporarily unavailable the collections still return and a warning says the members were not filled.

Mastodon Collections API FAQ

Which servers return collections?

Servers running Mastodon 4.7 or later that have collections enabled. Older Mastodon servers and forks without the route return lookupStatus unsupported with an empty collections list.

How many credits does it 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.

Are member accounts always filled?

Each item has accountId. The full account is filled when available. When it is not, the collections still come back and the response carries a parse warning, so account can be null.

Does this endpoint page?

No. It returns the account's collections in one response. Use the profile, posts and follower routes for the account's other data.