POST /api/crates/packages/search
Price: 5 credits
Search crates.io Rust crates by query, category, keyword, owner, or letter
Search Rust crates on crates.io by query text, category, keyword(s), owner, or starting letter, with configurable sorting (relevance, downloads, recent downloads, recent updates, newest, alphabetical). Returns each crate's name, description, links, download counts, version info, keywords and categories.
access-token string requiredtimeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)query string nullable — Search query matched against crate name and description (examples: "http client", "serde")count integer required — Number of crates to return (min: 1)sort string — Result ordering (default: "relevance"; one of: "relevance", "downloads", "recent-downloads", "recent-updates", "new", "alpha")category string nullable — Filter by category slug (examples: "web-programming", "no-std::no-alloc")keyword string nullable — Filter by a single keyword (examples: "http")all_keywords string nullable — Filter by multiple space-separated keywords (all must match) (examples: "http async")user_id integer nullable — Filter to crates owned by this user idteam_id integer nullable — Filter to crates owned by this team idletter string nullable — Filter to crates starting with this letter (minLength: 1; maxLength: 1)@type string (default: "CratesCrate")name string requireddescription string nullablehomepage_url string nullabledocumentation_url string nullablerepository_url string nullabledownload_count integer (default: 0)recent_download_count integer (default: 0)version_count integer (default: 0)default_version string nullablenewest_version string nullablemax_version string nullablemax_stable_version string nullableis_yanked boolean (default: false)exact_match boolean nullablekeywords array (default: [])categories array (default: [])created_at string (default: "")updated_at string (default: "")web_url string (default: "")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.X-Error — Error message text (present only on error)X-Request-ID — Unique request identifierX-Execution-Time — Execution time in secondsX-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.