O_exportOrderKeys
Starts an asynchronous export of the keys from a wholesale order you own. The export is
processed in the background; poll O_orderExport
with the same entryToken to retrieve the download URL once the export has completed.
To list your API orders and discover their entryToken values, see
O_orders.
This mutation requires the wholesale buyer role on your account.
Contact Eneba support if you receive a 403 or an access-denied error.
Supported arguments
The following arguments are supported by O_exportOrderKeys mutation:
| Field | Type | Description |
|---|---|---|
input | O_API_ExportOrderKeysInput! |
Return type
The mutation returns theO_API_ExportOrderKeysResponse type.
Constraints
- The
entryTokenmust belong to a wholesale order owned by the authenticated user. - The order must be marked as wholesale — non-wholesale orders return an
order.export_keys_non_wholesale_ordererror. - Only one export is needed per order; calling again while a previous export is still valid simply starts a new run.
Example usage
Request
mutation ExportOrderKeys($input: O_API_ExportOrderKeysInput!) {
O_exportOrderKeys(input: $input) {
success
}
}Variables:
{
"input": {
"entryToken": "a1b2c3d4-1234-11ee-be56-0242ac120002"
}
}Response
{
"data": {
"O_exportOrderKeys": {
"success": true
}
}
}Once the mutation returns success: true, poll
O_orderExport with the same
entryToken until status becomes COMPLETED and downloadUrl is populated.