Export to S3
Export a DataSet to an S3 bucket. Export your DataSets to an S3 device of your choosing (this is an asynchronous call). You can check the status of your export by calling/api/query/v1/export/{datasetId}. Only one active export can run per DataSet at a time. If the data in the DataSet hasn’t changed since the last export, this endpoint returns the export information for the previous export instead of creating a new download. Use temporary AWS credentials whenever possible; if credentials are temporary, provide an AWS session token.
Security Considerations
To export a datasource, consumers must have at least read access to the DataSet. Any PDP policies applied will be enforced during the export. Once data is uploaded, security depends on the AWS S3 bucket settings. Ensure secure upload locations to prevent unauthorized access. Example: An administrator initiates an export of sensitive compensation data to an S3 location accessible by the entire company, bypassing internal security measures.Cross-Region Exports
Cross-region exports are currently unsupported. Ensure that theREGION setting in the payload matches the S3 bucket’s region.
Create Export
Playground
POSTEndpoint:
/api/query/v1/export/<DATASOURCE_ID>
Request Example
Response Examples
Export Status
Playground
GETEndpoint:
/api/query/v1/export/<DATASOURCE_ID>
Request Example
Response Example
Error Status Codes
| Status Code | Meaning |
|---|---|
| 200 | Request successful. Export initiated or retrieved. |
| 201 | Resource created. |
| 400 | Invalid request. Export cannot be created. |
| 401 | Access denied. Token is invalid or expired. |
| 403 | Insufficient permissions for export access. |
| 404 | Dataset ID not found in the customer instance. |
| 500 | Unexpected server error. |