DASENTER Connections
All connectors

The Dasenter API

Gives your own backend a secret key so it can talk to Dasenter directly — create an order the moment a customer checks out, add a product, or read back what's already there.

What you need

  • A Dasenter account with at least one store already created
  • Access to your own backend's code, so you can add one line to its .env file
  • Five minutes

Steps

  1. 1Log in to your Dasenter dashboard.
  2. 2At the top of the page, use the store switcher to pick the store you want to connect (skip this if you only have one store).
  3. 3Click Integrations in the left-hand menu.
  4. 4Find the card labeled "Dasenter API" and click the Set Up API button on it.
  5. 5Dasenter creates a real secret key and shows it to you once, right there on the screen. Copy the whole thing immediately — if you navigate away before copying it, you cannot see it again (you'd need to generate a new one).
  6. 6Open your own backend project — not a website page, the server code that runs privately on your computer or hosting provider.
  7. 7Paste the key into that backend's .env file (or wherever it keeps secret settings), on its own line, e.g. API_SECRET=nx_live_<the key you copied>.
  8. 8Save the file. This alone does nothing yet — now actually start (or restart) your backend so it reads the new value into memory.
  9. 9Pick one of the three examples below, matching whatever language your backend is written in, and swap in your real key and store ID.
  10. 10Run it. If you see a reply that starts with {"data": ..., you just connected successfully.

Real examples

Using curl (works in any terminal, no code required) — creates a real order

Bash

curl -X POST http://localhost:3001/api/orders \
  -H "Authorization: Bearer nx_live_<your-generated-key>" \
  -H "Content-Type: application/json" \
  -d '{
    "storeId": "your_store_id",
    "externalId": "ORDER-123",
    "customer": { "name": "Jane Doe" },
    "items": [{ "name": "Running Shoe", "quantity": 1, "price": 15000 }],
    "total": 15000
  }'

Using Node.js (18 or newer — fetch is already built in) — creates a real product

JavaScript

const res = await fetch('http://localhost:3001/api/products', {
  method: 'POST',
  headers: {
    Authorization: 'Bearer nx_live_<your-generated-key>',
    'Content-Type': 'application/json',
  },
  body: JSON.stringify({
    storeId: 'your_store_id',
    sku: 'SHOE-001',
    name: 'Running Shoe',
    price: 15000,
  }),
});
const result = await res.json();
console.log(result); // { data: { id: "...", sku: "SHOE-001", ... } }

Using Python (the requests library) — reads back the store's own orders

Python

import requests

response = requests.get(
    "http://localhost:3001/api/orders",
    params={"storeId": "your_store_id"},
    headers={"Authorization": "Bearer nx_live_<your-generated-key>"},
)
print(response.json())  # { "data": { "orders": [...], "total": 3, ... } }

What success looks like

Whatever language you used, the reply is real JSON shaped like {"data": ...} and, for a create call, a new order or product genuinely shows up in the Dasenter dashboard immediately — no refresh needed.

Common mistake

Saving the .env file does not, by itself, do anything — you must actually start (or restart) your backend afterward so it reads the new key into memory. Also: this key is for your backend only. Never paste it into a website's HTML, a mobile app, or anywhere a stranger could view your page source and read it — for a browser page, use the JavaScript SDK's separate public key instead.

Making Product Push/Pull supported

There is no separate "Push"/"Pull" button for this connector, because the direction is already reversed: your own backend calls `POST /api/products` (and `PATCH`/`GET`) whenever it wants, on its own schedule. There's nothing to configure to "make it supported" — it's a direct API call, always available the moment your key works.

What data actually comes through

The most complete connector: any 3-letter currency code, images, variants, categories, and up to 30 custom attributes all pass straight through. Order status (pending/confirmed/preparing/shipped/delivered/cancelled) can be set on creation and changed afterward with your own follow-up calls — there's no separate status-update endpoint restriction here.