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 Hospitality Tables API

The Hospitality Tables API from Paymentsense — 6 operation(s) for hospitality tables.

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

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

This API exposes 8 operations across 6 paths, and defines 21 schemas. It is described by OpenAPI 3.2.0, at version 3.0-beta.

Requests are made against a single base URL, https://your-host-here.test.connect.paymentsense.cloud/.

8 operations 6 paths 21 schemas 1 DELETE2 GET1 POST4 PUT

Metadata

The identity and technical contract details declared by the specification.

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

Authentication & Security 1

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

Paths & Operations 8

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

Hospitality Tables 8
GET
/pat/tables
Gets a list of all tables. This can be filtered by locked state, fully paid state and currency.
Tables 2 params → 200401401 500
POST
/pat/tables
Creates/Opens a table
OpenTable body → 201401401 409 422 500
GET
/pat/tables/{tableName}
Gets details for a specific table
Table 1 param → 200401401 404 500
DELETE
/pat/tables/{tableName}
Deletes/Closes a table. This removes the table from Connect and means it is no longer accessible from any endpoints. It is intended for use when a table is fully paid and closed on the EPoS and allow…
DeleteTable 1 param body → 204401401 404 422 422 422 500
PUT
/pat/tables/{tableName}/amount
Updates the amount on a table. The lastKnownAmount and lastKnownPaidAmount must be passed in to ensure that updates only take place when the EPoS has the latest table data. This is to help avoid scen…
TableAmount 1 param body → 204401401 404 422 422 422 423
PUT
/pat/tables/{tableName}/lock
Updates the lock on a table. The lastKnownAmount and lastKnownPaidAmount must be passed in to ensure that updates only take place when the EPoS has the latest table data. This is to help avoid scenar…
TableLock 1 param body → 204401401 404 422 422 422 423
PUT
/pat/tables/{tableName}/receipt
Updates the receipt on a table. The lastKnownAmount and lastKnownPaidAmount must be passed in to ensure that updates only take place when the EPoS has the latest table data. This is to help avoid sce…
TableReceipt 1 param body → 204401401 404 422 422 422 423
PUT
/pat/tables/{tableName}/waiterids
Updates the waiter ids on a table. The lastKnownAmount and lastKnownPaidAmount must be passed in to ensure that updates only take place when the EPoS has the latest table data. This is to help avoid…
TableWaiterIds 1 param body → 204401401 404 422 422 422 423

Schemas 21

The contract defines 21 schemas that model the data the API accepts and returns. The most detailed are table (10 properties), tablePayment (9 properties), tableLockUpdate (5 properties), tableCreation (5 properties). Each schema is shown below with its type and property counts.

tableCreation
object
5 properties 3 required
table
object
10 properties 10 required
tablePaymentList
array
receiptLineList_2
array
receiptLine
object
3 properties 1 required
tableList
array
receiptLineList
array
tableListWrapper
object
1 property
tableCreationResponse
object
2 properties 2 required
receiptLineTypeHospitality
string
tablePayment
object
9 properties 9 required
format
string
currency
string
tableDeletion
object
2 properties 2 required
tableLockUpdate
object
5 properties 3 required
tableAmountUpdate
object
3 properties 3 required
tableReceiptUpdate
object
3 properties 3 required
tableWaiterIdsUpdate
object
3 properties 3 required
receiptLineTypeRetail
string
receiptLine_2
object
3 properties 1 required
paymentMethod
string

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

paymentsense-hospitality-tables-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 PAC Reports API
Paymentsense PAC Reports (Ingenico Only) API
Paymentsense PAC Terminals 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 Hospitality Tables 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.