Narvar API
Narvar is an AI-powered post-purchase platform that helps retailers manage delivery promises, order tracking, returns, exchanges, and customer communications across the post-purchase journey. An unofficial API lets you programmatically pull orders, shipments, tracking events, returns, and return labels—and push updates like new orders, tracking numbers, and return requests back into Narvar.
What is Narvar?
Narvar is an AI-powered post-purchase platform that helps retailers manage delivery, returns, and customer communications to build loyalty and protect revenue. Used by 1,500+ global brands across apparel, footwear, beauty, electronics, and home goods, Narvar powers branded order tracking, delivery date estimates, returns and exchanges, proactive notifications, and delivery fraud prevention across the post-purchase journey.
Core product areas include:
- Track (branded, real-time order tracking pages and delivery estimates)
- Shield / Returns & Exchanges (self-service returns, exchanges, and return label generation)
- Promise (AI-powered delivery date estimates shown pre-purchase)
- Notify (multi-channel SMS and email post-purchase communications)
- Secure / Assist (delivery protection and delivery-claim fraud detection)
- Narvar Agentic (intelligent automation for post-purchase workflows)
Common data entities:
- Orders, Order Items, Customers, Shipping Addresses
- Shipments, Tracking Numbers, Carriers, Tracking Events
- Returns, Return Items, Return Reasons, Return Reference Numbers, Return Labels
- Exchanges, Refunds, Store Credit
- Notifications, Delivery Estimates, Delivery Exceptions
The Narvar Integration Challenge
Retailers run high-volume post-purchase workflows on Narvar every day, but turning Hub- and portal-driven processes into reliable API automation is non-trivial:
- Credential gating: API access requires creating a V2/V3 API account in the Narvar Hub and managing Client ID/Client Secret pairs, which differ per retailer and environment
- Split API surface: Orders, returns label generation, and tracking each have their own endpoints, identifiers, and payload shapes—there is no single unified object model
- Identifier sprawl: Orders are keyed by order number while returns use a separate return_reference_number, so cross-entity joins require careful mapping
- Carrier and OMS coupling: Tracking numbers are pushed from a retailer's OMS or shipping software, so data freshness depends on upstream integrations behaving correctly
- Retailer-specific configuration: Branded tracking, return policies, and notification rules are tuned per brand, so generic integrations break across tenants
- Limited self-serve docs: The full developer portal sits behind authentication, so endpoint coverage and limits are hard to discover without an active account
How Supergood Creates Narvar APIs
Supergood reverse-engineers Narvar's authenticated Hub flows and REST APIs to deliver a resilient, normalized API layer for your Narvar account—across Track, Returns, and the post-purchase data your team depends on.
- Handles HTTP Basic authentication with your Client ID/Client Secret and V2/V3 API tokens securely
- Maintains session continuity with automated credential rotation and change detection
- Normalizes responses across Orders, Shipments, Tracking, and Returns so you integrate once and rely on consistent objects
- Reconciles order numbers and return_reference_numbers into a coherent post-purchase data model
Use Narvar with AI agents: Narvar MCP Server →
Getting Started
- Schedule Integration Assessment
Book a 30-minute session to confirm your Narvar modules, API account setup, and authentication model.
- Supergood Generates and Validates Your API
We deliver a production-ready Narvar adapter tailored to your account configuration and entitlements.
- Deploy with Monitoring
Go live with continuous monitoring and automatic adjustments as Narvar evolves.
API Endpoints
Authentication
/authenticateAuthenticate to a Narvar account using Client ID/Client Secret and a V2/V3 API token via HTTP Basic auth, returning a session for downstream calls.
Orders
/ordersList and retrieve orders by order number, including customer details, items, and shipping addresses synced into Narvar.
Orders
/create_orderCreate or update an order on the Narvar portal so it can be tracked and made eligible for returns.
Tracking
/trackingPull shipment, carrier, tracking number, and tracking event data for an order's branded tracking experience.
Returns
/returnsRetrieve returns and exchanges by return_reference_number, including items, reasons, refunds, and status.
Returns
/return_labelFetch the return shipping label associated with a return_reference_number for an order processed through Narvar.
Use Cases
Centralize post-purchase order and tracking data
- Pull orders, items, and customer details from Narvar into a single warehouse - Stream shipment and tracking events to BI, CX, and notification tools - Reconcile delivery estimates and exceptions against carrier performance
Automate returns and exchange workflows
- Retrieve returns and exchanges by return_reference_number for downstream systems - Pull return labels and attach them to support and fulfillment workflows - Sync refunds, store credit, and return reasons into finance and analytics tools
Keep orders and tracking numbers in sync
- Push new orders and tracking numbers from your OMS or shipping software into Narvar - Update order status so branded tracking pages stay accurate - Trigger downstream notifications when shipment status changes
Power AI agents and self-service experiences
- Surface real-time order and return status to chatbots and support agents - Let agents initiate returns and fetch labels without portal clicks - Feed normalized post-purchase data into customer 360 and loyalty programs
Technical Specifications
Authentication
HTTP Basic auth with Client ID/Client Secret and V2/V3 API tokens handled in a managed session
Connectivity
Authenticated Narvar Hub flows plus the Orders, Tracking, and Returns Label Generation REST APIs
Response format
Normalized JSON across Orders, Shipments, Tracking, and Returns objects
Rate limits
Adaptive throttling tuned to your account to avoid Narvar-side limits
Session management
Automatic credential rotation and re-auth handling for expired tokens
Data freshness
Near real-time pulls for orders, tracking, and returns with optional scheduled batch syncs
Security
Encrypted credential vault, scoped access tokens, SOC 2-aligned controls, and audit logging
Webhooks
Event-style callbacks for order updates, shipment status changes, delivery exceptions, and return events
Latency
Sub-second reads on cached entities; multi-second writes when creating orders or returns
Throughput
Horizontally scaled workers sized to peak ecommerce and holiday-season volume
Reliability
Retry, backoff, and idempotency keys for order and return creation
Adaptation
Continuous monitoring of Narvar API and Hub changes and per-retailer configuration drift
Frequently asked questions
Narvar REST APIs use HTTP Basic authentication. You generate a Client ID and Client Secret by creating a V2/V3 API account under Advanced Settings > API Accounts in the Narvar Hub. Supergood handles these credentials and token rotation in a managed session.
Yes. Supergood normalizes data across the Orders, Tracking, and Returns Label Generation APIs, so you can pull order, shipment, return, and label data through one consistent surface even though Narvar exposes them as separate endpoints.
Narvar keys orders by order number and returns by a separate return_reference_number. Supergood reconciles these identifiers into a coherent post-purchase model so you can join an order to its shipments, returns, and labels without manual mapping.
Yes. Supergood supports creating and updating orders and syncing tracking numbers from your OMS or shipping software, so branded tracking pages and return eligibility stay accurate.
No. Supergood works with your existing Narvar account and API credentials. You only need an active Narvar Hub account with API access enabled for the modules you use.