/huggingface/collections/search

POST /api/huggingface/collections/search

Price: 5 credits

Search Hugging Face collections

How to use it

Search Hugging Face collections by keyword, owner, or contained item. Sort by trending, upvotes, or last modified. Returns matching collections with title, owner, upvotes, and their ordered items.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• q string nullable — Free-text search keyword (examples: "llm")
• owner string nullable — Filter by owner (org or user) (examples: "google")
• item string nullable — Filter to collections containing this item (examples: "models/google/gemma-4-31B-it")
• sort string nullable — Sort field (one of: "trending", "upvotes", "lastModified")
• count integer required — Max result count (min: 1)

Response

• @type string (default: "HuggingfaceCollection")
• alias string required
• url string required
• description string nullable
• theme string nullable
• is_gated boolean (default: false)
• is_private boolean (default: false)
• upvote_count integer nullable
• last_updated_at string nullable
• owner object nullable
  • @type string (default: "HuggingfaceCollectionOwner")
  • alias string required
  • fullname string nullable
  • type string nullable
  • image string nullable
  • plan string nullable
  • follower_count integer nullable
• items array (default: [])
  • @type string (default: "HuggingfaceCollectionItem")
  • id string required
  • type string nullable
  • position integer nullable
  • author string nullable
  • repo_type string nullable
  • pipeline_tag string nullable
  • gated union nullable
  • download_count integer nullable
  • like_count integer nullable
  • parameter_count integer nullable
  • tags array (default: [])
  • created_at string nullable
  • last_modified string nullable

Errors

• 422 — The request body did not validate Check the fields against this schema. A URN with the wrong prefix is the most common cause.
• 408 — The request ran past its time limit Raise `timeout` in the request body, up to the maximum this endpoint documents. Lowering `count` or turning off the `with_*` flags also helps, because less work finishes sooner.
• 412 — The entity was not found, or a precondition failed Retrying will not help: either the entity does not exist, or the input points at a different one.
• 429 — Too many requests: a rate limit or a usage window is exhausted When the response carries an X-Retry-After header, wait that many seconds and retry: the same number is in the body as `detail.retry_after`, and the limit clears once that window passes. The message in the body names the limit that was hit.
• 500 — Something broke on our side Retrying will not help. If it keeps happening, send us the X-Request-ID from the response headers.
• 529 — Rate limit reached, or the endpoint is overloaded Wait at least 30 seconds, then retry.

Response headers

• X-Error — Error message text (present only on error)
• X-Request-ID — Unique request identifier
• X-Execution-Time — Execution time in seconds
• X-Result-Count — How many records the body carries. 0 means an empty result, which is a normal answer and not by itself an error. A non-zero count can come back together with X-Error when the failure happened partway through — read this header and X-Error independently.
• X-Total-Available-Results — How many records exist for this query, when the endpoint can say. On a `dry_run` request this is the answer and the body is empty. It saturates: the endpoint's documented maximum means 'at least that many', any smaller number is exact.
• X-Warning — Present when the request body carried keys this endpoint does not document. They were ignored, so any filter you meant to apply through them did not apply. Check the spelling against this schema and retry.
• X-Retry-After — Seconds to wait before retrying. Present only on 429.