Integration Specifications
This article will help you learn about how Daasity replicates data from Duoplane, limitations to the data we can extract and where the data is stored in the Duoplane schema
Integration Overview
Duoplane is focused on the development of technology solutions to automate and manage business and supply chains of e-commerce businesses. It is a provider of drop-ship and operations for advanced order routing and inventory syncing.
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 Duoplane extractor is built based on this Duoplane API Documentation. The following endpoint is used by Daasity to replicate data from Duoplane:
Entity Relationship Diagram (ERD)
Click here to view the ERD for the Daasity Duoplane integration illustrating the different tables and keys to join across tables.
Duoplane Schema
The Daasity Duoplane 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.
Purchase Orders
Endpoint: Purchase Order
Update Method: UPSERT
Table Name: [
duoplane.purchase_orders]
Purchase Order Items
Endpoint: Purchase Order
Update Method: UPSERT
Table Name: [
duoplane.purchase_order_items]
Shipments
Endpoint: Shipment
Update Method: UPSERT
Table Name: [
duoplane.shipments]
Shipment Items
Endpoint: Shipment
Update Method: UPSERT
Table Name: [
duoplane.shipment_items]
Shipment Tracking Numbers
Endpoint: Shipment
Update Method: UPSERT
Table Name: [
duoplane.shipment_tracking_numbers]
Last updated