Vimeo Browse API
A deep listing route for tag and user feeds, with a lighter row than the video record.
GET /v1/vimeo/videos/browse1 credit Failed requests are free
About this endpoint
GET /v1/vimeo/videos/browse browses video lists. Give exactly one of tag or user. tag takes a tag in any script; user takes a handle, numeric id or the user<id> form. sort accepts date, alphabetical, duration, plays or likes, and page is 1-based.
Each row is a vimeoBrowseVideo: id, title, url, thumbnail and uploadedAt. The page block is lighter too: page, hasMore and nextCursor, with no perPage or total, because this list does not state them. Use the video route when you need the full record. This route is best effort and may be unavailable; an unavailable request is a temporary failure, not an empty list.
Vimeo Browse API FAQ
Should I use browse or the tag route?
Use tags/{tag}/videos for a tag feed with full video records and page metadata. Browse returns a lighter row and a lighter page block, and is useful when you need its sort options or its deeper paging.
Do I pass both tag and user?
No. Give exactly one. The schema refuses a request with both or neither.
Why are perPage and total missing?
This list does not state a page size or a total. The page block has page, hasMore and nextCursor only, so follow hasMore rather than comparing a total.
How many credits does a browse 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.
Other Vimeo endpoints
- VideoGET /v1/vimeo/videos/{videoId}
- EmbedGET /v1/vimeo/videos/{videoId}/embed
- CaptionsGET /v1/vimeo/videos/{videoId}/captions
- CommentsGET /v1/vimeo/videos/{videoId}/comments
- CreditsGET /v1/vimeo/videos/{videoId}/credits
- LikesGET /v1/vimeo/videos/{videoId}/likes
- UserGET /v1/vimeo/users/{user}
- User videosGET /v1/vimeo/users/{user}/videos