/modelscope/datasets/files

POST /api/modelscope/datasets/files

Price: 1 credit

List files in a ModelScope dataset repository

How to use it

List files in a ModelScope dataset repository with commit metadata. Returns file name, path, size, LFS flag, sha256, and last commit message/committer/date. Optionally scope to a branch or tag and a subfolder.

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 repository id ('owner/name') or full dataset URL (examples: "modelscope/clue"; minLength: 1)
• revision string — Branch or tag to read files from (default: "master")
• root string — Folder path inside the repository to list (default: "")
• count integer required — Max result count (min: 1)

Response

• @type string (default: "ModelScopeRepoFile")
• name string required
• path string nullable
• file_type string nullable
• size integer nullable
• is_lfs boolean (default: false)
• sha256 string nullable
• mode string nullable
• commit_message string nullable
• committer string nullable
• committed_at integer nullable
• revision 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.