Integration Specifications
This article will help you learn about how Daasity replicates data from Returnly, limitations to the data we can extract and where the data is stored in the Returnly schema.
Integration Overview
Returnly is a digital return-and-exchange platform for DTC brands. It allows customers to instantly shop again when making a return. Returnly pays for the new items up front and takes on the product risk, so orders ship right away, providing the ultimate shopping experience.
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 Returnly extractor is built based on this Returnly API documentation. The following endpoint is used by Daasity to replicate data from Returnly:
Entity Relationship Diagram (ERD)
Click here to view the ERD for the Daasity Returnly integration illustrating the different tables and keys to join across tables.
Returnly Schema
The Daasity Returnly 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.
Returns
Endpoint: Returns
Update Method: UPSERT
Table Name: [
returnly.returns]
Return Line Items
Endpoint: Returns
Update Method: UPSERT
Table Name: [
returnly.return_line_items]
Refunds
Endpoint: Returns
Update Method: UPSERT
Table Name: [
returnly.refunds]
Refund Vouchers
Endpoint: Returns
Update Method: UPSERT
Table Name: [
returnly.refund_vouchers]
Last updated