Integration Specifications
This article will help you learn about how Daasity replicates data from Order Desk, limitations to the data we can extract and where the data is stored in the Order Desk schema
Integration Overview
Order Desk automates and streamlines order management workflow with integrations to hundreds of e-commerce services.
This document provides context on what kind of data is being gathered through this extractor, which endpoints that data is coming from, and how the extracted tables relate to each other.
Integration Availability
This integration is available for:
Enterprise
API Endpoints
The Daasity Order Desk extractor is built based on this Order Desk API documentation. The following endpoint is used by Daasity to replicate data from Order Desk:
Entity Relationship Diagram (ERD)
Click here to view the ERD for the Daasity Order Desk integration illustrating the different tables and keys to join across tables.
Order Desk Schema
The Daasity Order Desk extractor creates these tables using the endpoints and replication methods listed. The data is mapped from source API endpoint to the table based on the mapping logic outlined in each table.
Orders
Endpoint: Orders
Update Method: UPSERT
Table Name: [
order_desk.orders]
Order Checkout Data
Endpoint: Orders
Update Method: UPSERT
Table Name: [
order_desk.order_checkout_data]
Order Metadata
Endpoint: Orders
Update Method: UPSERT
Table Name: [
order_desk.order_metadata]
Order Discount List
Endpoint: Orders
Update Method: UPSERT
Table Name: [
order_desk.order_discount_list]
Order Notes
Endpoint: Orders
Update Method: UPSERT
Table Name: [
order_desk.order_notes]
Order Items
Endpoint: Orders
Update Method: UPSERT
Table Name: [
order_desk.order_items]
Order Items Variation List
Endpoint: Orders
Update Method: UPSERT
Table Name: [
order_desk.order_items_variation_list]
Order Shipments
Endpoint: Orders
Update Method: UPSERT
Table Name: [
order_desk.order_shipments]
Last updated