Supported Integrations and Functions
Support is rolled out per integration + function. If you’d like support added for an integration or function, reach out to us and we’ll look into enabling it. This list is regularly updated as we enable on-demand syncs for more integrations.WMS
Available function names:get_productsget_ordersget_inbound_shipmentsget_returnsget_billsget_inventory_ledger
get_inventory is intentionally not supported for on-demand syncs. Inventory syncs always fetch a full snapshot from the integration regardless of the time window, so an on-demand sync over a custom range would not change what gets pulled. To refresh inventory, use POST /connections/{id}/sync or wait for the next scheduled sync.- Amazon —
get_orders,get_returns,get_products,get_bills,get_inventory_ledger - Bergen —
get_orders,get_inbound_shipments - Bleckmann —
get_orders,get_inbound_shipments,get_returns - BlueBox —
get_returns - Byrd —
get_orders,get_inbound_shipments,get_returns - Camelot —
get_orders,get_inbound_shipments - Canary7 —
get_orders,get_inbound_shipments,get_returns - Carton Cloud —
get_orders - Cirro —
get_orders,get_products - Crafty —
get_orders,get_inbound_shipments - Davinci —
get_orders,get_inbound_shipments,get_returns - DCL —
get_orders - Deposco —
get_bills,get_inventory_ledger - Extensiv 3PL Central —
get_orders,get_inbound_shipments,get_returns,get_products,get_inventory_ledger - FedEx Fulfillment —
get_orders - FFE —
get_orders,get_inbound_shipments,get_returns - Finale —
get_orders,get_inbound_shipments,get_returns - Fulfillment —
get_orders,get_returns - Fulfillment Lab —
get_orders - Helm WMS —
get_inbound_shipments - i-Fulfilment —
get_orders - Infoplus —
get_orders,get_inbound_shipments,get_returns,get_products,get_bills - Jazz Central —
get_orders - Leanafy —
get_inbound_shipments - Linnworks —
get_orders - Logicpod —
get_orders - Logiwa —
get_orders,get_inbound_shipments,get_returns,get_products,get_bills,get_inventory_ledger - Logiwa.io —
get_orders,get_inbound_shipments - Mayple —
get_orders - Nimble —
get_orders,get_inbound_shipments,get_returns,get_products - NFI —
get_orders - OSA Commerce —
get_orders,get_inbound_shipments,get_returns,get_products - Packem —
get_orders - Packiyo —
get_orders,get_returns,get_products - Rush Order —
get_orders,get_inbound_shipments,get_returns - Salesupply —
get_orders - ShipBob —
get_orders - ShipHero —
get_orders,get_inbound_shipments,get_products,get_inventory_ledger - Shipping Tree —
get_inbound_shipments - ShipStation —
get_orders - ShipStream —
get_inbound_shipments,get_returns - Skulabs —
get_orders - SkyVault —
get_orders - Smart Warehousing —
get_orders - Sojo —
get_orders,get_inbound_shipments - Stord —
get_orders,get_inbound_shipments - TikTok —
get_orders - Vertical Cold —
get_orders,get_inbound_shipments - Walmart —
get_orders,get_returns - Warehance —
get_orders,get_products - Whiplash —
get_orders - Xorosoft —
get_orders,get_inbound_shipments
Carrier
Available function names:get_invoice_line_items
- DHL Express —
get_invoice_line_items - DPD —
get_invoice_line_items - FedEx —
get_invoice_line_items - Royal Mail —
get_invoice_line_items - UPS —
get_invoice_line_items - USPS —
get_invoice_line_items
Cart
On-demand syncs are not currently enabled for any Cart integrations.Usage
There are three endpoints for managing on-demand syncs:| Operation | Method | Path |
|---|---|---|
| Create a sync job | POST | /connections/on-demand-syncs |
| Get sync job status | GET | /connections/on-demand-syncs/{sync_job_id} |
| Cancel a sync job | POST | /connections/on-demand-syncs/{sync_job_id}/cancel |
Creating a Sync Job
Request Parameters
The following parameters are required when creating a sync job via the API:ISO 8601 timestamp marking the start of the time window to sync (e.g.,
2025-12-01T00:00:00Z).ISO 8601 timestamp marking the end of the time window to sync (e.g.,
2026-01-01T00:00:00Z).The data-fetching function to run. Must be one of the values listed in Supported Functions.
400 response with the message:
- Create via API
- Create via Dashboard
Checking Sync Job Status
Use thesync_job_id returned from the create call to check progress. The response includes a status field with one of the following values:
| Status | Meaning |
|---|---|
open | The job has been created and is either queued or actively running. |
completed | The job finished successfully. Synced data is now available via the standard Trackstar API. |
cancelled | The job was cancelled before it could finish (see Cancelling a Sync Job). |
open → completed. A cancelled job follows open → cancelled. Only jobs in the open state can be cancelled.
The full response also includes id, connection_id, function_name, requested_start_time, requested_end_time, and created_at.
- Check via API
- Check via Dashboard
Use the
sync_job_id returned from the create call:Cancelling a Sync Job
If a sync job is no longer needed, you can cancel it before it completes. Only jobs in theopen state can be cancelled.
- Cancel via API
- Cancel via Dashboard
Important Notes
- Asynchronous execution: Sync jobs run in the background. Poll the status endpoint or rely on Trackstar’s existing webhooks (e.g.
order.created,order.updated) to know when new data has landed. - Precedence over scheduled syncs: On-demand syncs take precedence over scheduled syncs on the same connection. While a sync job is in the
openstate, the regularly scheduled syncs for that connection will not run, which can cause recent data to fall behind. Once all open sync jobs finish (or are cancelled), scheduled syncs automatically resume from where they left off — so no data is missed, only delayed.



