How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

NCR Site API

Site (location) provisioning, lookup, and geospatial search.

NCR Site API is one of 7 APIs that NCR Voyix publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Site. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, a getting-started guide, and code examples.

This API exposes 6 operations across 5 paths, and defines 7 schemas. It is described by OpenAPI 3.2.0, at version 1.0.

Requests are made against 2 base URLs: https://api.ncr.com, https://gateway-staging.ncrcloud.com.

6 operations 5 paths 7 schemas 3 GET2 POST1 PUT

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
1.0
Base URL
https://api.ncr.com
Authentication
API Key
Resource Areas
1

Authentication & Security 1

NCR Site API declares 1 security scheme for authenticating requests. An API key is passed in the header as Authorization (hmacAccessKey). By default, every request must be authenticated.

  • hmacAccessKey — AccessKey (HMAC) authentication. The Authorization header carries "AccessKey {sharedKey}:{signature}", where the signature is a Base64 SHA-512 HMAC computed ov…

Paths & Operations 6

Across 5 paths, the API surfaces 6 operations — 3 GET, 2 POST, 1 PUT. Each is listed below with its method, path, parameters, and response codes.

Site 6

Site (location) provisioning, lookup, and geospatial search.

POST
/site/sites
NCR Voyix Create Site
createSite body → 201
GET
/site/sites/{siteId}
NCR Voyix Get Site by Id
getSiteById 1 param → 200404
PUT
/site/sites/{siteId}
NCR Voyix Update Site
updateSite 1 param body → 200
POST
/site/sites/find-by-criteria
NCR Voyix Find Sites by Criteria
findSitesByCriteria 1 param body → 200
GET
/site/sites/find-nearby/{coordinates}
NCR Voyix Find Nearby Sites
findNearbySites 3 params → 200
GET
/site/sites/by-reference-id/{referenceId}
NCR Voyix Get Site by Reference Id
getSiteByReferenceId 1 param → 200404

Schemas 7

The contract defines 7 schemas that model the data the API accepts and returns. The most detailed are SiteInput (8 properties), Address (5 properties), SiteSearch (2 properties), Coordinates (2 properties). Each schema is shown below with its type and property counts.

Error
object
2 properties
SiteInput
object
8 properties 3 required
Address
object
5 properties
Status
string
Site
Coordinates
object
2 properties
SiteSearch
object
2 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

ncr-site-api-openapi.yml Raw ↑

Other APIs NCR Voyix publishes across the network.

NCR Catalog API
NCR Category API
NCR Order API
NCR Provisioning API
NCR Security API
NCR Selling API
Where this information came from

This is an independent, third-party profile of NCR Site API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.