The API Report CardAPI Index
NCR Counterpoint

NCR Counterpoint API

POS / Hospitality · ncr.com

NCR Counterpoint's REST API is an on-prem Windows service installed at each merchant site, documented on GitHub. Getting in means an authorized reseller, a paid per-merchant CP API registration, and Basic auth with an APIKey header. No webhooks; integrators poll or read SQL Server.

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

SCORECARD

ExistencePOORThe REST API is an on-prem Windows service installed per merchant site (port 52000), not a hosted platform endpoint.
AccessPOORAccess runs through an authorized reseller plus a paid per-merchant CP API registration; no self-serve developer signup.
CoveragePOORCustomers, items, and tickets are covered, yet integrators still fall back to direct SQL Server access and the Integration Agent.
AuthPOORHTTP Basic auth with Counterpoint user credentials plus an APIKey header; no OAuth or scoped tokens.
Docs & DXPOORDocs are fragmented across a GitHub guide, a knowledgebase, and reseller portals; no webhooks, so integrators poll or use SQL triggers.
StabilityMIXEDVersion sprawl across 8.5.x and 8.6.x installs forces per-merchant feature detection; the API server does span versions.
Supergood: NCR Counterpoint has an API, but using it means gates, contracts, or workarounds. Ours doesn't: stable endpoints, normalized JSON, managed auth.

Frequently asked questions

NCR Counterpoint scores D+ on the API Report Card. NCR Counterpoint's REST API is an on-prem Windows service installed at each merchant site, documented on GitHub. Getting in means an authorized reseller, a paid per-merchant CP API registration, and Basic auth with an APIKey header. No webhooks; integrators poll or read SQL Server.

Tried to integrate with NCR Counterpoint?
SOURCES
Paid per-merchant API license (registration.ini option) plus partner gating - small ISVs face real cost-of-onboarding per customer site github.com
API Server is an on-prem Windows service per merchant - integrators must coordinate installation, firewall, port 52000 exposure, and patching with each customer's IT github.com
No native webhooks/event stream - third parties poll the REST API or read SQL Server directly, leading to stale data and tight coupling github.com
Multi-version sprawl (CPSQL 8.5.x, 8.6.x, service packs) - integrations have to feature-detect or branch per merchant install userportal.counterpointpos.com
Documentation is fragmented across a public GitHub repo, a CPSQL knowledgebase, the userportal.counterpointpos.com end-user portal, and reseller-maintained sites counterpoint.knowledgebase.co
Many integrations still rely on the older CPSQL Integration Agent / direct SQL Server access rather than the REST API, doubling the integration surface area radiantretailapps.com
Roadmap/ownership ambiguity after NCR Voyix split makes partners nervous about long-term API investment ipaas.com
Poor / slow technical support, especially after the NCR Voyix split - long hold times and unresolved tickets even for 10+ year customers capterra.com
Newer service-pack releases described as buggy with regressions; slow report performance and occasional system freezes during busy retail days trustradius.com
Untrustworthy inventory in some deployments - sales not always decrementing on-hand quantities, multi-location stock visibility limited softwareadvice.com
Steep learning curve - feature-rich but UX is dated Windows fat-client; significant training required for new staff softwareconnect.com
Customization (columns, reports, screens) often requires paid VAR engagement rather than self-service itqlick.com
On-prem-first architecture - upgrades, service packs, and hardware refreshes are the merchant's problem, not NCR's userportal.counterpointpos.com
Roadmap uncertainty after NCR Voyix split and concurrent investment in Aloha/Cumulus - merchants worry Counterpoint is in maintenance mode infotech.com