# Retrieve an organization data export request Retrieve an organization data export request with a specified organization ID. Endpoint: GET /organization-exports/{id} Version: latest Security: SecretApiKey, JWT ## Path parameters: - `id` (string, required) ID of the resource. ## Response 200 fields (application/json): - `id` (string) Unique resource ID. Example: "org_exp_01HXC7MKK4GCS6WRRXY4X9CRMK" - `userId` (string) ID of the user who requested the organization data export. Example: "usr_0YVCEENYJ3D7Q9EN6BN16HA0G4" - `fileId` (string,null) ID of the linked file object. Example: "file_0YV7HZ7KDCC5WBV9Q7WRKG1H6N" - `status` (string) Status of organization data export request. Enum: "pending", "processing", "completed", "queued", "failed", "expired" - `resources` (array) Organization data export resources array. - `resources.type` (string) Exported resource. Enum: "customers", "users", "payment-instruments", "invoices", "orders", "transactions", "disputes", "gateway-accounts", "blocklists", "lists", "webhooks", "products", "websites", "plans", "credit-memos", "files", "email-notifications" - `resources.recordCount` (integer) Number of exported resources. - `createdTime` (string) Date and time which is set automatically when the resource is created. - `updatedTime` (string) Date and time which updates automatically when the resource is updated. - `retentionTime` (string,null) Date and time when retention ends. After this date, files are removed. - `_links` (array) Related links. - `_links.href` (string) Link URL. - `_links.rel` (string) Type of link. Enum: "self", "user", "signedLink" ## Response 401 fields (application/json): - `status` (integer) HTTP status code. - `type` (string) Problem type in the form of a [URI](https://tools.ietf.org/html/rfc3986) reference. It should provide human-readable documentation for the problem type. When this member is not present, its value is assumed to be "about:blank". - `title` (string) Short, human-readable summary of the problem type. Other than for the purposes of localization, this should not change from occurrence to occurrence of the problem. - `detail` (string) Human-readable explanation that is specific to this occurrence of the problem. - `instance` (string) URI reference that identifies the specific occurrence of the problem. It may or may not yield further information if dereferenced. ## Response 403 fields (application/json): - `status` (integer) HTTP status code. - `type` (string) Problem type in the form of a [URI](https://tools.ietf.org/html/rfc3986) reference. It should provide human-readable documentation for the problem type. When this member is not present, its value is assumed to be "about:blank". - `title` (string) Short, human-readable summary of the problem type. Other than for the purposes of localization, this should not change from occurrence to occurrence of the problem. - `detail` (string) Human-readable explanation that is specific to this occurrence of the problem. - `instance` (string) URI reference that identifies the specific occurrence of the problem. It may or may not yield further information if dereferenced. ## Response 404 fields (application/json): - `status` (integer) HTTP status code. - `type` (string) Problem type in the form of a [URI](https://tools.ietf.org/html/rfc3986) reference. It should provide human-readable documentation for the problem type. When this member is not present, its value is assumed to be "about:blank". - `title` (string) Short, human-readable summary of the problem type. Other than for the purposes of localization, this should not change from occurrence to occurrence of the problem. - `detail` (string) Human-readable explanation that is specific to this occurrence of the problem. - `instance` (string) URI reference that identifies the specific occurrence of the problem. It may or may not yield further information if dereferenced.