Integration Specifications

This article will help you learn about how Daasity replicates data from Narvar, limitations to the data we can extract and where the data is stored in the Narvar schema

Integration Overview

Narvar is an e-commerce package tracking platform that allows you to keep customers up-to-date with timely order status notifications. With Narvar, you can track shipments around the world and provide estimated delivery dates your customers can rely on.

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 Narvar extractor is built based on this Narvar API documentation. The following endpoints are used by Daasity to replicate data from Narvar:

Entity Relationship Diagram (ERD)

Click here to view the ERD for the Daasity Narvar integration illustrating the different tables and keys to join across tables.

Narvar Schema

The Daasity Narvar 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: [narvar.returns]

Items

  • Endpoint: Returns

  • Update Method: UPSERT

  • Table Name: [narvar.items]

Exchange Options

  • Endpoint: Returns

  • Update Method: UPSERT

  • Table Name: [narvar.exchange_options]

Transactions

  • Endpoint: Returns

  • Update Method: UPSERT

  • Table Name: [narvar.transactions]

Fee Breakdown

  • Endpoint: Returns

  • Update Method: UPSERT

  • Table Name: [narvar.fee_breakdown]

Last updated