noon_impex_CreateExport
Start a noon export (a report file) and return its export_code at once; noon builds the file asynchronously.
readnoonnoon
noon API · ImpexService_CreateExport · POST /impex/v1/export/create Docs: https://noon-docs.noonpartners.dev/docs/api-reference/impex/impex-service-create-export
Call it
In an AI client (MCP)
{
"name": "noon_impex_CreateExport",
"arguments": {
"store": "myStore-US",
"exportCategoryCode": "<exportCategoryCode>"
}
}From code (Tool API)
curl -X POST https://api.sellersheetai.com/api/v1/tools/noon_impex_CreateExport \
-H "Authorization: Bearer $SELLERSHEET_API_KEY" \
-H "Content-Type: application/json" \
-d '{"store":"myStore-US","exportCategoryCode":"<exportCategoryCode>"}'Early access — the Tool API is open on request, contact us.
Arguments
| Name | Type | Description |
|---|---|---|
storerequired | string | the noon account ref `<account>-<CC>` (name-country, e.g. 'myNoon-AE') — one of get_user_context's noon store_refs, verbatim. |
exportCategoryCoderequired | string | a code from noon_impex_GetExportCategoryList (a known code the list omits is still sent as-is and noon decides), e.g. 'fbn_inventoryv2_aging' (no params), 'noon_noonoms_ordersexport' (params.from_date + params.to_date), 'noon_catalog_catalogexport' (params.noon_status 'live' or 'not_live'). |
params | object | the category's params (names from noon_impex_GetExportCategoryList). Dates are 'YYYY-MM-DD'. `country` / `country_code` is filled from the store ref (lowercased where noon needs it) and `lang` defaults to 'en' when the category takes them — pass them only to override. |
Result
Every tool answers {notification, data, human_action}; data carries:
data.export_code— pass it as exportCode to noon_impex_GetExportStatus.
Workflow
- 1. noon_impex_GetExportCategoryList — pick a code and its required params. 2. This tool. 3. noon_impex_GetExportStatus until export_status is COMPLETE, then noon_impex_download_export.