Crunchtime · Schema
ScheduledBatchExportFiles
ScheduledBatchExportFiles description
CompanyRestaurant OperationsInventoryLabor & SchedulingFood CostKitchen DisplayPoint-of-SaleSupply ChainHospitalityREST APIFood and Beverage
Properties
| Name | Type | Description |
|---|---|---|
| batchId | integer | Batch Number for export file. Required to retrieve file contents through downloadScheduledExport. |
| exportDate | string | Export Date of the export file. |
| exportStatus | integer | Export Status of the export file: (1) Manually created exports (“N/A” in Outbound Integrations); (2) Scheduled Export file ready for download (“CDP No” in Outbound Integrations); (3) Scheduled Export |
| exportType | string | "exportType" from scheduled export |
| extractHistoryId | integer | Numeric identifier for the individual export file. Required to retrieve file contents through downloadScheduledExport. |
| extractName | string | Export file type (or mapping) name. |
| fileName | string | File name of the individual export file. |
| postDate | string | Post Date for file contents, if applicable. Note that some USER_DEFINED files are assigned a file-level Post Date of 12/31/1990 even if their contents are Post Date-specific. |
| user | string | User ID of the Application User associated with the individual export file. This is the value displayed in the “User” column in Outbound Integrations for the relevant file or file batch and correlates |
JSON Schema
{
"$schema": "https://json-schema.org/draft/2020-12/schema",
"$id": "https://raw.githubusercontent.com/api-evangelist/crunchtime/main/json-schema/crunchtime-scheduled-batch-export-files-schema.json",
"title": "ScheduledBatchExportFiles",
"description": "ScheduledBatchExportFiles description",
"x-generated": "2026-10-14",
"x-method": "derived",
"x-generator": "derive-json-schema.py",
"x-source": "openapi/crunchtime-cruise-platform-openapi.yml#/components/schemas/ScheduledBatchExportFiles",
"type": "object",
"properties": {
"batchId": {
"type": "integer",
"format": "int64",
"description": "Batch Number for export file. Required to retrieve file contents through downloadScheduledExport."
},
"exportDate": {
"type": "string",
"description": "Export Date of the export file."
},
"exportStatus": {
"type": "integer",
"format": "int32",
"description": "Export Status of the export file: \n(1) Manually created exports (“N/A” in Outbound Integrations); \n(2) Scheduled Export file ready for download (“CDP No” in Outbound Integrations); \n(3) Scheduled Export file already downloaded by CDP or “marked” as downloaded (“CDP Yes” in Outbound Integrations); \n(5) Returns records Marked as not successfully downloaded (uncommon, but may happen with CDP download attempt)."
},
"exportType": {
"type": "string",
"description": "\"exportType\" from scheduled export",
"enum": [
"EMPLOYEE_MAINTENANCE",
"EPICOR_PLATINUM",
"INVENTORY_TOTALS",
"MAPPABLE_AP_TRANS_TYPE",
"MAPPABLE_AR_TRANS_TYPE",
"MAPPABLE_CUSTOM_TRANS_TYPE",
"MAPPABLE_EMPLOYEE_POS_TYPE",
"MAPPABLE_INVENTORY_DELTA_TYPE",
"MAPPABLE_INVENTORY_TOTALS_TYPE",
"MAPPABLE_LABOR_SCHEDULE_TYPE",
"MAPPABLE_LOC_TRANSFERS_TYPE",
"MAPPABLE_PAYROLL_TYPE",
"MAPPABLE_SALES_TYPE",
"MAPPABLE_STANDARD_AP_TYPE",
"PAYROLL",
"SALES",
"STANDARD_AP",
"STANDARD_INVENTORY_DELTA",
"STANDARD_LOCATION_TRANSFERS",
"USER_DEFINED"
]
},
"extractHistoryId": {
"type": "integer",
"format": "int64",
"description": "Numeric identifier for the individual export file. Required to retrieve file contents through downloadScheduledExport."
},
"extractName": {
"type": "string",
"description": "Export file type (or mapping) name."
},
"fileName": {
"type": "string",
"description": "File name of the individual export file."
},
"postDate": {
"type": "string",
"description": "Post Date for file contents, if applicable. Note that some USER_DEFINED files are assigned a file-level Post Date of 12/31/1990 even if their contents are Post Date-specific."
},
"user": {
"type": "string",
"description": "User ID of the Application User associated with the individual export file. This is the value displayed in the “User” column in Outbound Integrations for the relevant file or file batch and correlates to the “userIdForDetails” query param."
}
}
}
Work with this as data
Every JSON Schema here is available over the APIs.io API and to AI agents over MCP.
MCP server
One button, every client — Claude, Cursor, VS Code and the rest.
https://apis.io/mcp
Tools for schemas
4 MCP tools reach this
find_json_schemasBrowse and filter every JSON Schema in the catalog.apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.resolveTurn a domain, URL or GitHub org into the provider it belongs to.find_cohortsEvery scored population of providers in the catalog.
Call it yourself
curl for this page
This JSON Schema
curl "https://apis.io/api/v1/json-schemas/crunchtime-scheduled-batch-export-files"
All schemas
curl "https://apis.io/api/v1/json-schemas?limit=25"
Discovery needs no key. Ratings and market analysis are Pro.
Get an API key
Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.
A second provider on the same verified email joins the account you already have.