Data Config — Adperical RDN

API Key

Use this key to authenticate your POS data feed. Keep it secret.

••••••••••••••••••••••••

Last ingestion: Loading...

API Stats

Total Transactions

--

Total API Calls

--

Unique Stores

--

Date Range

--

Test Endpoint

Send a test POST to verify your integration.

curl -X POST https://adperical.com/api/rdn/ingest \
  -H "Content-Type: application/json" \
  -H "X-API-Key: YOUR_API_KEY" \
  -d '{
    "store_id": "STORE-001",
    "customer_id": "phone:+961XXXXXXXX",
    "items": [
      {"sku": "SKU-1234", "category": "beverages", "brand": "Coca-Cola", "qty": 2, "amount": 4.50},
      {"sku": "SKU-5678", "category": "snacks", "brand": "Doritos", "qty": 1, "amount": 3.99}
    ],
    "total": 8.49,
    "timestamp": "2026-03-30T23:42:00Z"
  }'

Data Format

Field	Type	Required	Description
`store_id`	string	Yes	Unique store identifier
`customer_id`	string	No	Customer identifier — phone (phone:+961XXXXXXXX) or email (user@example.com). Hashed on ingestion.
`customer_email`	string	No	Customer email address (will be hashed)
`items`	array	Yes	Array of purchased items
`items[].sku`	string	Yes	Product SKU
`items[].category`	string	Yes	Product category
`items[].brand`	string	No	Brand name
`items[].qty`	number	Yes	Quantity purchased
`items[].amount`	number	Yes	Line item total
`total`	number	Yes	Transaction total
`timestamp`	ISO 8601	No	Transaction timestamp (defaults to now)

Bulk Upload

Upload a CSV (one row per line item) or JSON file as an alternative to the API. Headers are flexible — both our field names and common POS export headers are accepted:
store_id (Store No_), store_name (Store Name), timestamp (Date Time), sku (Item No_), item_name (Description), category (Item Category), brand (Item Family), qty (Quantity Sold), amount (Sales Amount), transaction_id (Receipt No_), phone, email, customer_id (Customer Member Account), is_promo (Promotion), is_ecomm (E-Commerce) (total is optional — computed from line items when absent)

Phones are normalized to E.164 (e.g. +96170123456) and emails to lowercase before hashing. We store SHA-256 hashes compatible with Meta Custom Audiences (digits-only phone) and Google Customer Match (E.164 phone) — never the raw values. Rows are grouped into one transaction by Receipt No_ / transaction_id when present, otherwise by timestamp + store + identity.

📄 Drop your CSV or JSON file here or click to browse CSV (.csv) or JSON (.json) — up to ~100 MB, parsed in your browser and uploaded in batches

Data Configuration