The API Report CardAPI Index
Narvar

Narvar API

Post-Purchase / Retail Ecommerce · narvar.com

Narvar has a real REST API and first-class returns webhooks, but the developer docs sit behind a merchant login on its support center. Auth is HTTP Basic only, with credentials from the merchant portal. Public artifacts are limited to a status page and partial third-party specs.

Last verified: July 2026Retail & Ecommerce
API GRADE
D
VERIFIED JUL 2026

SCORECARD

ExistencePOORA returns and RMA REST API exists, but the first-party reference sits behind a merchant login; only partial specs are public.
AccessPOORRequires a merchant relationship; credentials are created in the merchant portal and the docs need a merchant login to read.
CoveragePOORReturns and RMA flows are the documented surface, plus a refund approval endpoint; broader tracking data lacks a public reference.
AuthPOORHTTP Basic Auth only; no OAuth, API key header, or JWT is documented publicly.
Docs & DXPOORFirst-party docs sit behind a merchant login on the support center; public artifacts are a status page and third-party specs.
StabilityMIXEDWebhook events carry version, signature, and replay protection headers, but lifecycle policy sits behind the merchant login.
Supergood: Narvar has an API, but using it means gates, contracts, or workarounds. Ours doesn't: stable endpoints, normalized JSON, managed auth.

Frequently asked questions

Narvar scores D on the API Report Card. Narvar has a real REST API and first-class returns webhooks, but the developer docs sit behind a merchant login on its support center. Auth is HTTP Basic only, with credentials from the merchant portal. Public artifacts are limited to a status page and partial third-party specs.

Tried to integrate with Narvar?