Skip to content

Acknowledge a repo's failed or finished upload so the feed stops reporting it

POST
/v1/datasets/uploads/{repo_id}/dismiss
curl --request POST \
--url https://example.com/v1/datasets/uploads/2489E9AD-2EE2-8E00-8EC9-32D5F69181C0/dismiss \
--header 'Content-Type: application/json' \
--header 'X-API-Key: <X-API-Key>' \
--data '{ "dismissed_through_unix": 0 }'

Dismiss, not destroy: QDS records a per-repo watermark that suppresses the repo’s terminal entries (failed and finalized, and the quiet staging rows a failure falls back to) at or older than the entry the caller saw. The failure record itself is kept — it is the only account of why the ingest failed — and no storage is reclaimed. A live upload cannot be dismissed: preparing/publishing are never suppressed, and staging only after the transfer has stopped taking new manifests, so a click that races a running attempt returns the live phase instead of hiding it.

A sub-resource of the feed it edits, not of /datasets/{dataset_id}: a failed upload has minted no dataset. POST rather than DELETE for the same reason — nothing is deleted, and it carries a body.

repo_id
required
string format: uuid
account_id

Act on this account (active)

string | null format: uuid

Act on this account (active)

Media type application/json
DismissUploadBody
object
dismissed_through_unix
integer
0

Successful Response

Media type application/json
Example generated
example

Invalid or missing API key

Media type application/json
ErrorResponse

Standard error response.

object
detail
required

Error message describing what went wrong

string
Example generated
{
"detail": "example"
}

Validation Error

Media type application/json
HTTPValidationError
object
detail
Array<object>
ValidationError
object
loc
required
Location
Array<string | integer>
msg
required
Message
string
type
required
Error Type
string
input
ctx
Context
object
Example generated
{
"detail": [
{
"loc": [
"example"
],
"msg": "example",
"type": "example",
"input": "example",
"ctx": {}
}
]
}