Retrieve Dataset Metadata | Dadosfera AutoDriveDDF API.

Time	Status	User Agent
Retrieving recent requests…

Time

Status

User Agent

Retrieving recent requests…

Description

Retrieve full metadata for one dataset.

Use this endpoint to read-only check:

Whether a newly-uploaded dataset has finished processing (status = "success").
Immutable properties such as created_at, updated_at, and customer_name.
The dataset’s current ingestion state (status_reason if the state ≠ success).

HTTP Request

GET /dataset/{dataset_id}

Location	Name	Type	Required	Description
Path	`dataset_id`	string	✓	UUID returned at upload time, e.g. `c8004e22-87f7-441f-8302-80c934841196`.

Authentication

In your REST client (Postman/Insomnia), select Basic Auth and enter your Username and Password.

The client will automatically generate the Authorization: Basic … header for you. Do not add that header manually.

Required Headers

Header	Example	Notes
Accept	`application/json`	Optional – guarantees JSON output.

Example Request (cURL)

curl -u admin:myPassword \
     https://api.autodriveddf.example/dataset/c8004e22-87f7-441f-8302-80c934841196

Success Response (`200 OK`)

{
  "dataset_id": "c8004e22-87f7-441f-8302-80c934841196",
  "name": "platform_knowledge_base",
  "status": "success",
  "status_reason": null,
  "customer_name": "dadosferaDemo",
  "instance_id": "78b9e8c0-a123-4e56-9f01-abcdef123456",
  "created_at": "2025-05-04T14:46:58.802Z",
  "updated_at": "2025-06-10T09:30:12.500Z"
}

Field	Type	Description
`dataset_id`	string	Canonical UUID for this dataset.
`name`	string	Human-readable name assigned at upload.
`status`	string	One of `success`, `processing`, or `failed`.
`status_reason`	string	Null on success; otherwise a brief reason for failure.
`customer_name`	string	Tenant / account identifier.
`instance_id`	string	Internal processing instance (for audit/debug only).
`created_at`	string	ISO-8601 timestamp when the dataset was first uploaded.
`updated_at`	string	ISO-8601 timestamp of the most recent file addition or metadata update.

Error Responses

Code	Reason	When it happens	Sample Body
401	Unauthorized	Missing / wrong Basic Auth credentials	—
404	Not Found	`dataset_id` does not exist or is hidden	`{ "detail": "Dataset not found" }`
500	Internal ServerError	Unexpected server failure	`{ "detail": "Unexpected error occurred" }`

Idempotency

GET /dataset/{dataset_id} is idempotent and read-only — repeated calls return the same metadata unless the dataset itself changes (e.g., new documents uploaded via PUT /dataset/{dataset_id}).