Skip to main content

Export Privacy Request Data

GET 

/v1/privacy/requests/export/:id

Export the data of the Privacy Request with a specific ID.

List and item endpoints for requests and consents, together with the export endpoint, require core.admin on com_privacy. There is no consent DELETE route.

Creation, confirmation, export and removal are separate stages. Creating a request does not complete export or delete a user. The export action requires request_type: "export" and confirmed status 1; otherwise the model supplies no export data and the view raises a route-not-found exception.

Privacy plugins supply the export domains, but the API serialises their array as one resource. Its attributes can therefore be an array of domain names and descriptions, with an empty resource ID. Protected domain items are not included by that serializer. A missing ID can also raise a PHP warning and fail under stricter error handling. Do not treat this response as a complete personal-data export or as the export file produced in the administrator. Use the administrator export workflow when you need that complete result. There is no generic PATCH or DELETE workflow for request records. The base edit check requires core.manage and record core.edit, or core.edit.own with a matching owner; component overrides take precedence. Omitted SERVER_UTC/USER_UTC calendar values are restored from the stored UTC values after validation, avoiding a second timezone conversion.

Request​

Responses​

Successful response.