The API Report CardAPI Index
Wine POS

Wine POS API

POS / Hospitality · winepos.com

WinePOS offers an API and a Data Extract service, but integration is partner-mediated: no developer portal, no published spec, no self-serve keys. Inventory feeds are daily batch or FTP; only the UPS and FedEx shipping integrations use modern OAuth, provisioned in carrier portals.

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

SCORECARD

ExistenceGOODA WinePOS API and a Data Extract feed service exist for custom integrations, alongside FTP inventory feeds.
AccessPOORNo self-serve keys; ISVs and retailers engage WinePOS support to get credentials and field mappings.
CoveragePOORItem and inventory extracts are daily batch feeds; there is no real-time event access.
AuthPOORAuth differs per path: API keys, FTP uploads, and carrier OAuth provisioned in UPS and FedEx portals.
Docs & DXPOORNo developer portal, published API reference, or OpenAPI spec; scoping starts with a call to WinePOS.
StabilityMIXEDLegacy FTP and batch extracts coexist with newer OAuth shipping APIs; ISVs often support several paths at once.
Supergood: Wine POS has an API, but using it means gates, contracts, or workarounds. Ours doesn't: stable endpoints, normalized JSON, managed auth.

Frequently asked questions

Wine POS scores D+ on the API Report Card. WinePOS offers an API and a Data Extract service, but integration is partner-mediated: no developer portal, no published spec, no self-serve keys. Inventory feeds are daily batch or FTP; only the UPS and FedEx shipping integrations use modern OAuth, provisioned in carrier portals.

Tried to integrate with Wine POS?
SOURCES
No public developer portal, no published API reference - integrations require contacting WinePOS to scope and provision access winepos.com
Data Extract service is batch/daily-refresh oriented (file-based item/inventory feeds), not real-time webhook/event streaming winepos.com
FTP file uploads still used for inventory sync to online channels - operationally fragile vs. modern push APIs winepos.com
UPS API modernization required every retailer to manually re-provision OAuth Client ID/Secret and a callback URL in their UPS developer account, with similar work required for FedEx (Production API Key + Secret + label DPI certification) winepos.com
Multiple integration paths (WinePOS API, Data Extract, FTP, WineFetch shipping APIs) with different auth and data models - ISVs often must support more than one to cover the install base winepos.com
eCommerce partners (CityHive, BottleCapp) effectively act as middleware between WinePOS sites and modern commerce/delivery surfaces, adding a hop and another vendor for retailers cityhive.net
High upfront cost - pricing reported to start around $1,500, with full deployments running materially higher; no public tier pricing softwareadvice.com
Legacy Windows-based architecture; UI feels dated compared to cloud-native competitors (Square, Lightspeed, KORONA) softwareworld.co
Limited self-serve onboarding - implementation is sales-led and requires coordination with the WinePOS team for installation and training selecthub.com
Customer support handled primarily by phone/email/ticket queue with limited after-hours coverage for a 24/7 retail vertical sourceforge.net
Reporting and customization seen as less flexible than general-purpose retail POS platforms getapp.com
Vertical lock-in - migrating away from WinePOS to a modern cloud POS is a heavy data-migration project (item DB, vendors, customers, loyalty, multi-year sales history) posnation.com