/kaggle/datasets

POST /api/kaggle/datasets

Price: 1 credit

Get Kaggle dataset details by owner/slug or dataset URL

How to use it

Get full details of a Kaggle dataset by 'owner/slug' or a Kaggle dataset URL. Returns title, subtitle, description, owner, license, size in bytes, vote/download/view/kernel counts, usability rating, current version number, last updated time, thumbnail image, tags, and the version history.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• dataset string required — Dataset as 'owner/slug' or a Kaggle dataset URL (examples: "heptapod/titanic", "https://www.kaggle.com/datasets/heptapod/titanic"; minLength: 1)

Response

• @type string (default: "KaggleDataset")
• id integer required
• ref string required
• alias string required
• subtitle string nullable
• description string nullable
• owner string nullable
• owner_ref string nullable
• creator_name string nullable
• license_name string nullable
• size_bytes integer (default: 0)
• vote_count integer (default: 0)
• download_count integer (default: 0)
• view_count integer (default: 0)
• kernel_count integer (default: 0)
• topic_count integer (default: 0)
• usability_rating number nullable
• current_version_number integer nullable
• is_private boolean (default: false)
• is_featured boolean (default: false)
• image string nullable
• web_url string nullable
• updated_at string nullable
• tags array (default: [])
  • @type string (default: "KaggleTag")
  • ref string required
  • name string required
  • full_path string nullable
• versions array (default: [])
  • @type string (default: "KaggleDatasetVersion")
  • version_number integer required
  • status string nullable
  • version_notes string nullable
  • creator_name string nullable
  • creator_ref string nullable
  • created_at 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 — Dataset not found 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.