Gumroad Tags API
Tag names with site-wide use counts, matched by prefix or ranked by use.
GET /v1/gumroad/tags1 credit Failed requests are free
About this endpoint
GET /v1/gumroad/tags takes an optional query and answers { data, meta } with data.lookupStatus always found, data.query and data.tags. Each tag has name and uses, the site-wide use count.
The match is a prefix match, not a substring match: not finds notion but not a tag that merely contains those letters. An empty or omitted query returns the most used tags. The list is capped at 10 and sorted by use, so it is a small picker list rather than a full tag index. There is no paging.
Gumroad Tags API FAQ
Is the match a prefix or a substring?
A prefix. query=not matches tags that start with not, such as notion. It does not match a tag that only contains the letters later in the word.
What does uses count?
uses is the site-wide number of products that carry the tag. It is the marketplace's count, not a count for one creator or one search.
Why are there at most 10 tags?
The route returns the top 10 by use, which is the size the product filter needs. Narrow the query if the tag you want is not in the list.
Can an empty result mean an error?
No. A prefix with no matching tags answers found with an empty tags array. lookupStatus is always found on this route.
How many credits does a tags request 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 Gumroad endpoints
- ProductGET /v1/gumroad/product
- Product detailsGET /v1/gumroad/product/details
- ReviewsGET /v1/gumroad/product/reviews
- Related productsGET /v1/gumroad/product/related
- Call slotsGET /v1/gumroad/product/call-slots
- SearchGET /v1/gumroad/search
- SuggestionsGET /v1/gumroad/search/suggestions
- CategoriesGET /v1/gumroad/categories