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

Paymentsense PAC Terminals API

The PAC Terminals API from Paymentsense — 3 operation(s) for pac terminals.

Paymentsense PAC Terminals API is one of 18 APIs that Paymentsense publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include PAC Terminals. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, and an API reference.

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

Requests are made against 2 base URLs: https://your-host-here.test.connect.paymentsense.cloud/, https://dev-heisenberg.test.connect.paymentsense.cloud.

3 operations 3 paths 5 schemas 3 GET

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
1.0
Base URL
https://your-host-here.connect.paymentsense.cloud
Authentication
HTTP Basic
Resource Areas
1

Authentication & Security 1

Paymentsense PAC Terminals API declares 1 security scheme for authenticating requests. It accepts HTTP basic authentication (connectBasicAuth). By default, every request must be authenticated.

Paths & Operations 3

Across 3 paths, the API surfaces 3 operations — 3 GET. Each is listed below with its method, path, parameters, and response codes.

PAC Terminals 3
GET
/pac/terminals
Gets a list of all card terminals that are currently connected. This can be filtered by currency, capabilities and status.
RetailTerminals 3 params → 200401401 500
GET
/pac/terminals/{tpi}
Gets details for a specific terminal.
RetailTerminalsByTPI 1 param → 200401401 404 500
GET
/pac/terminals/{tid}
Gets details for a specific terminal.
PACTerminalsByTID 1 param → 200401404422500

Schemas 5

The contract defines 5 schemas that model the data the API accepts and returns. The most detailed are terminal (5 properties), terminal_2 (4 properties), userMessage (1 property), terminalWrapper (1 property). Each schema is shown below with its type and property counts.

terminal
object
5 properties 5 required
terminalList
array
terminalWrapper
object
1 property
terminal_2
object
4 properties 4 required
userMessage
object
1 property

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

paymentsense-pac-terminals-api-openapi.yml Raw ↑

Other APIs Paymentsense publishes across the network.

Paymentsense Connect WebSockets API
Paymentsense Access Token API
Paymentsense Cross Reference Payment API
Paymentsense Hospitality Reports API
Paymentsense Hospitality Tables API
Paymentsense PAC Reports API
Paymentsense PAC Reports (Ingenico Only) API
Paymentsense PAC Transactions API
Paymentsense PAT Reports API
Paymentsense PAT Tables API
Paymentsense Payment Details API
Paymentsense Payment Methods API
Where this information came from

This is an independent, third-party profile of Paymentsense PAC Terminals 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.