Configuring Dafiti as a Source
In the Sources tab, click on the “Add source” button located on the top right of your screen. Then, select the Dafiti option from the list of connectors. Click Next and you’ll be prompted to add your access.1. Add account access
Dafiti Seller Center authenticates API access with an OAuth application that you create inside your own Seller Center account. It gives you an Application ID and an Application Secret.1
Open OAuth Applications
Sign in to Dafiti Seller Center and open Settings → Integration Management → OAuth Applications.
2
Create the application
Click Add Application (top right corner), give it a name such as
Nekt, and save.3
Copy the credentials
Copy the Application ID and the Application Secret shown for the new application.
- Application ID: the Application ID of the OAuth application. Required.
- Application Secret: the Application Secret shown together with the Application ID. Required.
- Start Date: the earliest date of orders and financial transactions to extract. Leave it empty to extract the full history.
- Lookback Days: how many days are re-read before the last sync point on orders and financial transactions, so records changed while a sync was running are never missed. The default is 7.
- Window Days: the size, in days, of each date range requested from Dafiti. The default of 30 fits most accounts.
- Requests Per Second: how fast the connector may call Dafiti. Seller Center allows 30 requests per second per seller, and that budget is shared with every other integration connected to your account (ERP, hub, marketplace manager). The default of 5 leaves room for them.
2. Select streams
Choose which data streams you want to sync. For faster extractions, select only the streams that are relevant to your analysis. You can select entire groups of streams or pick specific ones.Tip: The stream can be found more easily by typing its name.
Order Items come from the same requests as Orders, so selecting them adds no extraction time. Product Stocks, on the other hand, makes one request per product set — on large catalogs it is the slowest stream, so deselect it if you do not need stock levels.
3. Configure data streams
Customize how you want your data to appear in your catalog. Select the desired layer where the data will be placed, a folder to organize it inside the layer, a name for each table (which will effectively contain the fetched data) and the type of sync.- Layer: choose between the existing layers on your catalog. This is where you will find your new extracted tables as the extraction runs successfully.
- Folder: a folder can be created inside the selected layer to group all tables being created from this new data source.
- Table name: we suggest a name, but feel free to customize it. You have the option to add a prefix to all tables at once and make this process faster!
- Sync Type: Orders, Order Items, and Finance Transactions support INCREMENTAL. The catalog streams, Finance Statements, and Seller are extracted in full on every run. Read more about Sync Types here.
4. Configure data source
Describe your data source for easy identification within your organization, not exceeding 140 characters. To define your Trigger, consider how often you want data to be extracted from this source. This decision usually depends on how frequently you need the new table data updated (every day, once a week, or only at specific times). Optionally, you can define some additional settings:- Configure Delta Log Retention and determine for how long we should store old states of this table as it gets updated. Read more about this resource here.
- Determine when to execute an Additional Full Sync. This will complement the incremental data extractions, ensuring that your data is completely synchronized with your source every once in a while.
5. Check your new source
You can view your new source on the Sources page. If needed, manually trigger the source extraction by clicking on the arrow button. Once executed, your data will appear in your Catalog.Things to know
- Customer data is masked by Dafiti. Restricted fields of the billing and shipping addresses, such as email and phone, come masked from the API.
- Transactions follow their statement. A transaction belongs to the open statement (
statement_id0) until the statement closes. The connector re-reads the open statement and the statements closed since the last sync, sostatement_idis updated when a statement closes. - Only active categories. The category tree returned by Dafiti contains active categories only.
Streams and Fields
Below you’ll find all available data streams from Dafiti and their corresponding fields. API reference: Seller Center REST API.Orders
Orders
Marketplace orders (
GET /v2/orders). Every sync reads the orders created or with an item changed since the last sync, re-reading the last 7 days by default.Primary key: id · Replication key: updated_atOrder Items
Order Items
One row per item of each order, with price, discounts, commission, shipment and invoice data. Expanded from the order payload, so it adds no extraction time.Primary key:
id · Replication key: order_updated_atProduct Sets
Product Sets
Every product set of your catalog, in any status (
GET /v2/product-sets?status=all). A product set groups the variations (sizes) of a product.Primary key: id · Full tableProducts
Products
Every sellable variation (usually one per size) of your product sets (
GET /v2/products).Primary key: id · Full tableProduct Stocks
Product Stocks
Current stock of every product, including consignment and warehouse breakdowns. Seller Center only exposes stock per product set, so this stream makes one request per product set.Primary key:
product_set_id, seller_sku · Full tableProduct Prices
Product Prices
Regular and sale price of every product, one row per product and country (
GET /v2/prices).Primary key: product_id, country · Full tableBrands
Brands
Brands available to your seller account (
GET /v2/brands).Primary key: id · Full tableCategories
Categories
The active category tree, flattened to one row per category (
GET /v2/category/tree).Primary key: id · Full tableFinance Transactions
Finance Transactions
Financial transactions of your account — item prices, commissions, shipping fees, refunds, and adjustments — for both marketplace and consignment statements (
GET /v2/finance/transactions).Primary key: id · Replication key: dateFinance Statements
Finance Statements
Account statements: the payout periods with their balances, due dates, and payment status (
GET /v2/finance/statements).Primary key: id, type · Full tableSeller
Seller
The seller account the OAuth application belongs to (
GET /v2/seller).Primary key: id · Full table