The API Report CardAPI Index
THE API REPORT CARD / Retail & Ecommerce / Paladin Data Corporation
Paladin Data Corporation

Paladin Data Corporation API

POS / Hospitality · paladinpos.com

Paladin's e-commerce REST API covers three endpoints: inventory reads, completed invoice posting, and OAuth 2.0 tokens. The spec is a PDF in a GitHub repo, the sandbox is an Excel file, and Paladin Support must enable access store by store; items only sync when flagged per SKU.

Last verified: August 2026Retail & EcommerceNO MCP
API GRADE
D+
VERIFIED AUG 2026

SCORECARD

ExistencePOOROne REST e-commerce API with just Inventory, Invoice, and Token endpoints, specced in a PDF inside a GitHub repo.
AccessPOORPaladin Support must manually enable API access per store; developer contact is email-only, with no signup or portal.
CoveragePOORInventory reads and invoice posting only: no orders, customers, employees, or reporting; items must be flagged Ext Sync per SKU.
AuthPOOROAuth 2.0 token flow, but credentials and per-store base URLs are issued manually by support at enablement time.
Docs & DXPOORThe spec is a PDF in a GitHub repo and the sandbox is an Excel test store file; no OpenAPI, webhooks, or published rate limits.
StabilityMIXED
MCPNONENo official or community MCP server was found for Paladin Data Corporation. Neither the official MCP registry nor GitHub shows any server targeting the Paladin point of sale platform. VERIFIED 2026-08
Supergood turns hard-to-integrate enterprise software into clean REST APIs and MCP tools: stable endpoints, normalized JSON, managed auth.

Frequently asked questions

Paladin Data Corporation scores D+ on Supergood's API Report Card. Paladin's e-commerce REST API covers three endpoints: inventory reads, completed invoice posting, and OAuth 2.0 tokens. The spec is a PDF in a GitHub repo, the sandbox is an Excel file, and Paladin Support must enable access store by store; items only sync when flagged per SKU.

Tried to integrate with Paladin Data Corporation?
SOURCES
No public OpenAPI spec - the API contract lives in a PDF inside a GitHub repo and is updated infrequently github.com
Integration enablement is manual - Paladin Support must turn on each store's API access after the integrator builds against the spec, no self-serve developer signup portal.paladinpos.com
Catalog is gated per-SKU by the 'Ext Sync' checkbox in the Inventory module - integrators get partial inventory views unless the retailer flags every product portal.paladinpos.com
Sandbox is an Excel test-store file (PaladinEcomAPITestStore.xlsx) rather than a live sandbox tenant - hard to validate real-world flows github.com
Only two functional endpoints (Inventory + Invoice) plus Token - no orders, no customers, no employees, no reporting, no purchase orders surfaced in the public API github.com
No published rate limits, no public webhook catalog - partners must poll Inventory for stock changes github.com
Developer access is email-only (development@paladinpos.com) - no developer portal, no API keys provisioned online, no public-facing docs site beyond a help-portal knowledge-base article github.com
Per-tenant / per-store API hosts mean integrators must wire each retailer onboarded individually rather than hitting a single multi-tenant endpoint portal.paladinpos.com
Pharmacy integration is a separate C# COM service definition (PharmacyCOMv1) rather than part of the REST API - dispensing-system integrators run a parallel, Windows-bound integration path github.com
Reports are not configurable - operators must request custom reports rather than self-serve, and per-day analysis must be done day-by-day rather than month-at-a-time capterra.com
Cannot add items to a transaction post-completion; users say they were promised continuous fixes but 'just learn to live with' product gaps capterra.com
Cloud/server outages of 1 to 1.5 hours documented by long-tenured pharmacy customers; store-down events disrupt prescription pickup capterra.com
UI feels slow and glitchy in places - 'hit enter or use the mouse about 5 times to get to where you want to go' capterra.com
Sales/billing complaints: monthly fee creep, hardware over-sell at install, full monthly charge billed despite mid-cycle cancellation checkthat.ai
Promised features (e.g., rental department) discovered to be unsupported after contract signing checkthat.ai
Windows-based terminal stack feels dated next to cloud/iPad-native competitors (Lightspeed, Shopify POS, Korona) softwareadvice.com
Customization and feature requests routed through Paladin support as 'special requests' rather than user-configurable settings capterra.com
Multi-store and franchise features less robust than Epicor Eagle for larger Ace/Do it Best member co-ops softwareadvice.com