- swiftpos Help Guides
- API
- Orders API
-
Installers / Links / Releases
-
API
-
Back Office
-
Back Office Cloud
-
Events
-
Events Portal
-
How To
- API
- Back Office
- Clerks / Staff
- Cloud
- Combos
- Customers / Members
- Doshii
- Events
- Events Portal
- Guests
- Interfaces
- Items / Products
- KVS
- Member Portal
- NetPOS
- Notify
- Oolio Pay
- OrderAway
- Orders / Sales
- POS Keys
- Self Service
- SevenRooms
- swiftPOS
- Tables
- Thirsty Camel Hump Club
- Touch
- TouchMini
- TouchMini v2
- Venue Hub
- Venue Manager
- XERO
- XERO Pro
- Zen Global
-
Interfaces
-
KVS
-
Member Portal
-
Notify
-
Oolio Pay
-
OrderAway
-
POS Keys
-
Self Service Kiosk
-
Self Service POS
-
swiftpos
-
Touch
-
TouchMini
-
TouchMini v2
-
Troubleshooting
-
Venue Manager
-
Venue Hub
-
Uncategorized
About

This provides an overview of the swiftpos Orders API, a Cloud based API that is required to submit Orders/Sales to swiftpos.
The content is targeted at Resellers and swiftpos Venue Administrators who have a sound knowledge of and experience with swiftpos. For further information or assistance, please contact your swiftpos Reseller or swiftpos Support.
Subjects ▼
What Is It? ▲ ▼
The swiftpos Orders API is a Cloud based API (Rest API) and is a rebrand of the formerly known MSL Connect API or Connect API. It is used to submit Orders/Sales to swiftpos. Orders may be directed to either:
- Back Office - Orders/Sales are sent to swiftpos Touch via Table Tracking, OR
- Touch - The preferred Direct to POS method, that makes use of the swiftpos POS API (pos-api.swiftpos.com.au) installed on a Touch Terminal.
It is primarily used to receive Orders/Sales from external applications, such as:
It also supports the Direct to POS Terminal Front of House Connection Method.
It makes use of the swiftpos Gateway Client Service to establish connectivity with the SwiftPOS POS API and the SwiftPOS Back Office API to post/pull Member, Product, Sales and Voucher data directly from/to the swiftpos Back Office Database.

End of article. ▲