---
title: "Get all exports"
method: POST
path: "/api/connector/v1/exports/getAll"
tags: ["Exports"]
---

# Get all exports

`POST /api/connector/v1/exports/getAll`

Returns exports for the given `ExportIds`. This operation supports [Portfolio Access Tokens](https://mews-systems.gitbook.io/connector-api/concepts/multi-property/).

## Request body

- ExportFilterParameters
  - `ClientToken` string, required — Token identifying the client application.
  - `AccessToken` string, required — Access token of the client application.
  - `Client` string, required — Name and version of the client application.
  - `ExportIds` string[], required — Unique identifiers of the [Exports](https://mews-systems.gitbook.io/connector-api/operations/#export).

## Response `200`

OK

- ExportResult
  - `Exports` Export[], required — Requested exports.
    - `Id` string, uuid, required — Unique identifier of the export.
    - `Status` 'Pending' | 'Processing' | 'Success' | 'Failed' | 'Expired', required — Current status of the export. Pending Processing Success Failed Expired
    - `EntityType` 'OrderItem' | 'Payment' | 'Reservation' | 'Customer' | 'Company' | 'Bill' | 'AvailabilityAdjustment' | 'AvailabilityBlock' | 'ResourceBlock' | 'LedgerEntry', required — Type of exported entities OrderItem Payment Reservation Customer Company Bill AvailabilityAdjustment AvailabilityBlock ResourceBlock LedgerEntry (**Beta testing - subject to change.** See [Ledger entry type](https://docs.mews.com/connector-api/operations/_export-types#ledger-entry).)
    - `Scope` ExportScope, required
      - `EnterpriseIds` string[], nullable — Unique identifiers of enterprises for which the data is exported.
      - `ChainIds` string[], nullable — Unique identifiers of chains for which the data is exported.
    - `Files` ExportFileEntry[], required — Files with exported data. Empty if no files are available or the export is expired.
      - `Url` string, uri, required — Download URL for the exported file in JSON Lines format. The link remains valid for 10 minutes after it is returned.
      - `SizeInBytes` integer, required — Total size of the exported file in bytes.
    - `ExpiresUtc` string, date-time, nullable — Expiration date and time of the export in UTC timezone in ISO 8601 format. After this time the Exported files may no longer be available for download.
    - `Filters` ExportDataFilters
      - `UpdatedUtc` TimeFilterInterval — When a time interval is used for **filtering** (for example in parameters such as `CreatedUtc.StartUtc` / `CreatedUtc.EndUtc`), the following rules apply: - **Start equals End (equality mode)** If `StartUtc` and `EndUtc` are exactly the same timestamp, the filter is treated as an equality check for that precise moment in time: ``` CreatedUtc == StartUtc ``` This does not represent an interval; only records with `CreatedUtc` equal to that exact instant are returned. - **Start differs from End (interval mode)** If `StartUtc` and `EndUtc` are different, the filter is evaluated as a half-open interval: ``` StartUtc <= CreatedUtc < EndUtc ``` In other words, the start is inclusive and the end is exclusive. Make sure your integration takes inclusive Start / exclusive End behavior of time intervals into account so that no records at the boundaries are omitted.
        - `StartUtc` string, date-time, nullable
        - `EndUtc` string, date-time, nullable
      - `LedgerEntryFilters` ExportLedgerEntryDataFilters
        - `Posting` DateFilterInterval, required
          - `Start` string, date, required — Starting date of the interval in ISO 8601 format.
          - `End` string, date, required — Ending date of the interval in ISO 8601 format.

## Other responses

- `204` — Server has successfully fulfilled the request and there is no additional information to send back.
- `400` — Error caused by the client app, e.g. in case of malformed request or invalid identifier of a resource. In most cases, such an error signifies a bug in the client app (consumer of the API).
- `401` — Error caused by usage of invalid ClientToken, AccessToken, or you may not have the necessary permission to use the endpoint.
- `403` — Server error that should be reported to the end user of the client app. Happens for example when the server-side validation fails or when a business-logic check is violated.
- `408` — Error caused by heavy request that takes too long to process (typically tens of seconds). To get around this, request data in smaller batches. For more information, see [Request timeouts](https://mews-systems.gitbook.io/connector-api/guidelines/requests#request-timeouts)
- `429` — Error caused by too many requests sent in a given amount of time. Response contains `Retry-After` header indicating how long the user agent should wait before making a follow-up request. For more information, see [Request limits](https://mews-systems.gitbook.io/connector-api/guidelines/requests#request-limits).
- `500` — Unexpected error on the Mews side. This may be due to a software fault. If such a situation occurs, the error will be logged and the development team notified, however you can raise an issue through GitHub on our [documentation repository](https://github.com/MewsSystems/gitbook-connector-api).

---

[API](https://skmtc.dev/mews/apis/connector-api.md) · [All operations](https://skmtc.dev/mews/apis/connector-api/llms.txt) · [OpenAPI document](https://skmtc-service-production.skmtc.workers.dev/v1/apis/mews/connector-api/revisions/b5dc3b2c1e7d/schema)