Integrations

The API exposesProducts, categories and prices · Stock sources and quantities · Carts, orders and shipments · Customer accounts

Can be scoped for

• An in-store kiosk can show the same range and availability as the online store.
• Orders placed at a kiosk can be created in the store for fulfilment.

The API exposesProducts, variants and price lists · Inventory by location · Orders and customers · Webhooks for order and stock events

Can be scoped for

• A kiosk can act as another storefront on the same catalogue and stock.
• Stock changes can refresh the products shown on a display.

The API exposesProducts and price lists · Stock levels by warehouse · Sales orders and goods-out notes · Contacts and customers

Can be scoped for

• Kiosk orders can be sent to the same order and warehouse process as web and shop orders.

The API exposesProducts and stock on hand · Sales orders and purchase orders · Customers and suppliers · Stock adjustments and transfers

Can be scoped for

• A kiosk can check availability by location before an order is taken.
• Orders taken at a kiosk can be raised as sales orders.

The API exposesProduct catalogue and prices · Carts and orders · Inventory entries · Customers · Change messages through subscriptions

Can be scoped for

• Kiosk software can be built as one more front end on the same commerce back end.

The API exposesProducts and categories · Stock quantities · Orders and customers · Webhooks for order and product changes

Can be scoped for

• A small retailer can show and sell the same products at a kiosk as on their website.

The API exposesProducts, variants and materials · Stock levels by location · Sales orders and manufacturing orders · Webhooks for order and stock events

Can be scoped for

• Made-to-order products configured at a kiosk can be passed to production as sales orders.

The API exposesInventory items and stock levels · Open and processed orders · Stock locations · Shipping and despatch details

Can be scoped for

• Orders taken at a kiosk can join the same picking and despatch process as online orders.
• Stock levels can be read before a kiosk offers an item.

The API exposesProducts, categories and prices · Stock quantities · Carts and orders · Customer accounts

Can be scoped for

• A kiosk can browse and order from a self-hosted store without duplicating the catalogue.

The API exposesCarts and order creation · Customers · Shipping and payment methods · Vouchers and coupons

Can be scoped for

• Orders taken at a kiosk can be created in the store; reading the product range may need an extension or a data export.

The API exposesProducts, combinations and categories · Stock availability · Orders and carts · Customers and addresses

Can be scoped for

• A kiosk can present the store range and create orders against the same stock.

The API exposesProduct search and details · Baskets and orders · Inventory availability · Customer profiles

Can be scoped for

• In-store kiosks can extend an existing storefront with the same baskets, prices and promotions.

The API exposesProduct catalogue and prices · Carts and orders · Stock levels by point of service · Customer accounts

Can be scoped for

• A kiosk can be scoped as an in-store channel on an existing SAP commerce installation.

The API exposesProducts, variants and inventory levels · Orders and fulfilment · Customers · Webhooks for order and inventory events

Can be scoped for

• An in-store kiosk can browse the same catalogue and stock levels as the online store.
• Orders placed at a kiosk can be created in the store for fulfilment and reporting.

The API exposesProducts and categories · Stock and availability · Carts and orders · Customers

Can be scoped for

• A kiosk can use the storefront interface to browse the range and place orders.

The API exposesProducts and variants · Inventory quantities · Orders and fulfilment · Transactions

Can be scoped for

• A kiosk can show products from a Squarespace shop and adjust stock when an item is sold.

The API exposesProducts and stock on hand · Sales orders and shipments · Purchase orders · Customers and suppliers

Can be scoped for

• A trade-counter kiosk can check warehouse stock and raise a sales order.

The API exposesProducts and stock levels · Orders and allocations · Warehouses · Shipments

Can be scoped for

• Kiosk orders can be added alongside web orders for picking, packing and shipping.

The API exposesProducts and collections · Inventory · Orders and carts · Webhooks for store events

Can be scoped for

• A kiosk can list products from a Wix store and record orders against it.

The API exposesProducts, variations and categories · Stock quantities · Orders and refunds · Customers · Webhooks for order and product events

Can be scoped for

• A kiosk can sell from the same WooCommerce products and stock as the website.
• Orders placed at a kiosk can appear in WooCommerce for fulfilment and reporting.

The API exposesInventory items and categories · Orders and line items · Payments and refunds · Customers

Can be scoped for

• Kiosk orders can be written to the same order list and reports as till sales.

The API exposesProducts and categories · Stock levels · Transactions and tenders · Customers

Can be scoped for

• A kiosk can read the products and pricing held in the till system and post completed sales back.

The API exposesProducts and price lists · Inventory by location · Sales documents and payments · Customers and reward points

Can be scoped for

• A kiosk can sell from the chain-wide range and record each sale against the correct shop.

The API exposesMenus, items and modifiers · Orders sent to the point of sale · Payments and receipts · Reporting data

Can be scoped for

• Self-service orders can be sent to the till and kitchen as if taken by staff.
• Menu changes made in the till system can flow through to kiosks and menu boards.

The API exposesProducts and inventory · Sales and payments · Customers · Outlets and registers · Webhooks for sale and stock events

Can be scoped for

• A kiosk can sell from live shop stock and record the sale against the right outlet.

The API exposesItems, categories and modifiers · Receipts · Inventory levels · Customers · Webhooks for receipts and stock

Can be scoped for

• A kiosk can share the item list and send completed sales to the same back office.

The API exposesMenu and item data · Orders sent to the point of sale · Checks and payments · Site configuration

Can be scoped for

• Self-service orders can be sent to the restaurant system for kitchen routing and reporting.

The API exposesMenus, items and prices · Checks and orders · Tenders and payments · Revenue centres and sites

Can be scoped for

• Kiosk orders can be posted as checks so they reach kitchen displays and reports with counter sales.

The API exposesProducts and modifiers · Orders and payments · Customers · Establishments and inventory

Can be scoped for

• Self-service orders can be created in the same system as counter orders.

The API exposesItem library and categories · Inventory counts · Orders and payments · Customers and reward schemes · Webhooks for order and stock events

Can be scoped for

• A kiosk can take orders against the same items, stock and reports as the counter till.
• Orders can be shown on kitchen displays that already serve the counter.

The API exposesMenus and modifiers · Orders · Restaurants and configuration · Labour and reporting data

Can be scoped for

• Self-service orders can be sent to the restaurant system for preparation and reporting.

The API exposesOnline checkout and payment sessions · In-person payments through card terminals · Refunds and captures · Webhooks for payment outcomes

Can be scoped for

• Kiosk software can start a card payment on a connected terminal and receive the result.
• Unattended payment needs terminals and approval from the provider suited to that use.

The API exposesPayment requests on the web and in apps · Payment tokens passed to the processor · Wallet passes for tickets and membership cards

Can be scoped for

• Contactless wallet payments are accepted at a kiosk through the card terminal, with no separate connection needed.
• Web ordering reached from a kiosk by QR code can offer the wallet at checkout.

The API exposesTransactions and refunds · Stored payment methods · Customers and subscriptions · Webhooks for payment events

Can be scoped for

• Web or app ordering that accompanies a kiosk can take payment through the same gateway.

The API exposesPayments, captures and refunds · Payment links and hosted pages · Disputes · Webhooks for payment events

Can be scoped for

• A kiosk can show a payment link as a QR code so the customer pays on their own phone.

The API exposesCheckout creation · Payment capture and refunds · Order status

Can be scoped for

• Assisted-selling kiosks for higher-value goods can offer instalments where the merchant already has an agreement.

The API exposesPayment intents for online and in-person payments · Card machine connections for tills · Refunds · Webhooks for payment outcomes

Can be scoped for

• Ordering software can send the amount to a Dojo card machine and record the outcome against the order.

The API exposesOnline payment requests · Refunds and repeat payments · Tokens for stored cards · Transaction reporting

Can be scoped for

• Web checkout linked to a kiosk journey can take payment through the existing gateway of the merchant.

The API exposesPayments, captures and refunds · Payment links · Stored payment methods · Transaction reporting

Can be scoped for

• A kiosk can take card payment through terminals and services supplied under the agreement the merchant holds.

The API exposesCustomers and mandates · Payments and subscriptions · Instant bank payments · Webhooks for payment and mandate events

Can be scoped for

• A membership or subscription sign-up at a kiosk can set up a Direct Debit mandate.

The API exposesPayment requests on the web and in Android apps · Payment tokens passed to the processor · Wallet passes for tickets and membership cards

Can be scoped for

• Contactless wallet payments are accepted through the kiosk card terminal without a separate connection.
• Web ordering reached from a kiosk by QR code can offer the wallet at checkout.

The API exposesTerminal software development kits · Payment requests from a till or kiosk to the terminal · Terminal estate management

Can be scoped for

• An unattended terminal can be fitted to a kiosk and driven by the ordering software through the payment provider.

The API exposesPayment sessions and orders · Captures and refunds · In-store payment requests

Can be scoped for

• Showroom and assisted-selling kiosks can offer pay-later options where the merchant has an agreement.

The API exposesPayments and refunds · Payment links · Orders and subscriptions · Webhooks for payment status

Can be scoped for

• A kiosk can display a payment link as a QR code for payment on the phone of the customer.

The API exposesOrders and payment capture · Refunds · Invoices and payment links · Webhooks for payment events

Can be scoped for

• A kiosk can show a QR code so the customer completes payment in their own PayPal account.

The API exposesOrders and payments · Refunds · Payment links · Webhooks for order events

Can be scoped for

• A kiosk can create an order and present a payment link or QR code for the customer to pay.

The API exposesPayments and refunds · Terminal checkouts on Square devices · Payment links · Webhooks for payment events

Can be scoped for

• Kiosk software can request a payment on a Square terminal and receive the outcome.

The API exposesPayment intents and refunds · Customers and saved payment methods · Terminal readers for in-person payment · Payment links · Webhooks for payment events

Can be scoped for

• Kiosk ordering software can take card payment through a compatible reader, subject to the requirements for unattended use.
• Payment outcomes can be recorded against the order in the sales system.

The API exposesCheckouts and transactions · Card reader payments from an app or till · Payment links · Merchant and payout data

Can be scoped for

• A kiosk application can start a payment on a paired card reader and read back the result.

The API exposesInstant bank payments · Payment status and refunds · Payouts · Account and identity data with consent

Can be scoped for

• A kiosk can present a QR code that opens a pay-by-bank journey in the banking app of the customer.

The API exposesPayment requests and refunds · Stored card tokens · Transaction queries · Notifications of payment outcomes

Can be scoped for

• A kiosk can take payment through terminals or a gateway provided under the agreement the merchant holds.

The API exposesTerminal software development kits · Payment requests from a till or kiosk to the terminal · Cloud payment and reporting services

Can be scoped for

• An unattended Verifone device can be fitted to a kiosk and driven by the ordering software.

The API exposesOnline payments and refunds · Hosted checkout pages · Payment links · Webhooks for payment status

Can be scoped for

• Card payments at a kiosk can run through terminals and services supplied under the agreement the merchant holds.

The API exposesOnline payments, captures and refunds · Tokens for stored cards · In-person payments through integrated terminals · Webhooks for payment events

Can be scoped for

• A kiosk can be connected to an integrated card terminal so the amount is sent from the order automatically.

The API exposesProduct library · Purchases and payments · Inventory · Card reader payments from another application

Can be scoped for

• A kiosk application can request payment on a paired reader and log the sale in the account of the merchant.

The API exposesConnectors to common business applications · Interfaces published and managed on the platform · Scheduled and event-driven processes

Can be scoped for

• Where a company already runs its integrations on Boomi, kiosk data can be exchanged through that platform.

The API exposesTriggers and actions for connected services · Webhook triggers and requests · Applets with filters

Can be scoped for

• Simple alerts, such as a message when a kiosk enquiry arrives, can be set up without custom development.

The API exposesModules for a large range of applications · Webhook triggers and generic web requests · Scenarios with routing, filters and data mapping

Can be scoped for

• Enquiries and orders captured at a kiosk can be passed into a scenario that updates other systems.
• Content for displays can be assembled from sources that have no direct connection.

The API exposesConnectors for Microsoft and other services · Flows started by a web request · Approvals and notifications · Custom connectors

Can be scoped for

• A kiosk enquiry can start a flow that creates a record, notifies a team and files attachments.

The API exposesManaged interfaces to back-office systems · Connectors and data transformation · Event and message processing

Can be scoped for

• Kiosk software can consume interfaces that a company already publishes through its integration layer.

The API exposesNodes for common applications and databases · Webhook triggers and web requests · Custom code steps · Self-hosted deployment

Can be scoped for

• Workflows can run on a server the customer controls where kiosk data should stay within their network.

The API exposesFlows linking devices and web services · Message queue and serial device nodes · Web endpoints and dashboards

Can be scoped for

• Sensors, relays and other hardware around a kiosk can be linked to the kiosk software and to online services.

The API exposesTriggers and actions for many applications · Web request triggers · Code steps in common languages

Can be scoped for

• Event-driven hand-offs from kiosk software to other systems can be built and hosted without a separate server.

The API exposesConnectors for business applications · Webhook and scheduled triggers · Workflows with branching and data mapping

Can be scoped for

• Sales and enquiry data from kiosks can be routed to the business applications the customer already uses.

The API exposesConnectors for enterprise applications · Recipes started by events, schedules or web requests · Interface management

Can be scoped for

• Where a company has standardised on Workato, kiosk events can start recipes that update its other systems.

The API exposesTriggers and actions for thousands of applications · Webhook triggers and requests · Multi-step workflows with filters and formatting

Can be scoped for

• An enquiry captured at a kiosk can be passed on to systems that have no direct interface with the kiosk software.
• Routine hand-offs between a booking tool, a spreadsheet and an email list can be automated during scoping.

The API exposesContacts · Invoices and estimates · Bank transactions · Expenses and bills

Can be scoped for

• Daily sales totals from kiosks can be posted as invoices or as explanations of bank transactions.

The API exposesClients · Invoices and payments · Expenses · Items and services

Can be scoped for

• A service booked or paid for at a kiosk can raise an invoice against the client record.

The API exposesCustomers and vendors · Items and stock · Sales orders and invoices · General ledger entries · Webhooks for record changes

Can be scoped for

• Orders taken at a kiosk can be created as sales orders with stock and finance updated together.

The API exposesCustomers and items · Sales orders and invoices · Inventory by location · Saved searches and reporting data

Can be scoped for

• Kiosk sales can be recorded as orders or cash sales with stock updated in the same system.

The API exposesCustomers and suppliers · Invoices, sales receipts and payments · Items and accounts · Reports · Webhooks for record changes

Can be scoped for

• Daily kiosk takings can be posted as sales receipts, split by payment type and VAT rate.

The API exposesContacts · Sales invoices and credit notes · Products and services · Bank accounts and payments · Ledger accounts

Can be scoped for

• Sales from kiosks can be posted as invoices or takings against the correct ledger accounts.

The API exposesCustomers and vendors · Invoices and journal entries · Dimensions such as location and department · Reporting data

Can be scoped for

• Sales summaries from each site can be posted with the location recorded for reporting.

The API exposesContacts · Invoices, payments and credit notes · Items and tracked inventory · Bank transactions · Webhooks for contact and invoice changes

Can be scoped for

• Kiosk sales can be posted as daily invoices or takings, split by payment type and tax rate.
• Customer accounts created at a kiosk can be matched to contacts.

The API exposesContacts · Invoices and payments · Items · Expenses and bills

Can be scoped for

• Sales captured at kiosks can raise invoices or receipts in the accounts.

The API exposesPeople and organisations · Opportunities and pipelines · Tasks and notes · Webhooks for record changes

Can be scoped for

• An enquiry made at a kiosk can create a contact and an opportunity for the sales team.

The API exposesContacts and accounts · Deals and pipelines · Tasks and appointments · Notes and activities

Can be scoped for

• Leads captured at a showroom kiosk can be created as contacts with the products of interest attached.

The API exposesContacts, companies and deals · Forms and marketing events · Tickets and conversations · Webhooks for record changes

Can be scoped for

• Kiosk enquiries can create or update contacts and open a deal at the right pipeline stage.
• Consent captured at a kiosk can be stored against the contact for later marketing.

The API exposesLeads, contacts and accounts · Opportunities and quotes · Activities · Custom tables in Dataverse

Can be scoped for

• Leads captured at kiosks can be created against the correct owner, site and campaign.

The API exposesBoards, items and columns · Updates and files · Users and teams · Webhooks for item changes

Can be scoped for

• Enquiries from kiosks can arrive as items on a sales or operations board for follow-up.

The API exposesPeople and organisations · Deals and pipeline stages · Activities and notes · Products · Webhooks for record changes

Can be scoped for

• An enquiry at a kiosk can create a person and a deal with the chosen products attached.

The API exposesLeads, contacts and accounts · Opportunities and products · Custom objects · Platform events and change notifications

Can be scoped for

• Leads captured at kiosks can be created with their source, site and products of interest.
• Staff-facing kiosks can look up account details during assisted selling.

The API exposesTickets and comments · Users and organisations · Help centre articles · Webhooks and triggers

Can be scoped for

• A help point on a kiosk can raise a support ticket with the site and device details attached.
• Help centre articles can be shown on information kiosks.

The API exposesLeads, contacts and accounts · Deals and products · Custom modules · Notifications of record changes

Can be scoped for

• Leads from kiosks can be added with their source and assigned by the rules already in the system.

The API exposesContacts, lists and tags · Custom fields · Automations and campaigns · Webhooks for contact events

Can be scoped for

• A sign-up at a kiosk can add a contact with consent recorded and start a welcome sequence.

The API exposesContacts and lists · Transactional email and SMS · Campaigns · Webhooks for delivery and engagement events

Can be scoped for

• Order confirmations and collection messages can be sent by email or text from kiosk software.
• Newsletter sign-ups at a kiosk can be added to the right list with consent recorded.

The API exposesContacts and address books · Campaigns and programmes · Transactional email and SMS · Consent records

Can be scoped for

• Sign-ups and purchases at a kiosk can update the contact record that drives marketing programmes.

The API exposesContacts and companies · Conversations and messages · Help articles · Webhooks for conversation events

Can be scoped for

• A help option on a kiosk can open a conversation with the support team, with the device and site identified.

The API exposesProfiles and lists · Events and metrics · Catalogue items · Campaigns and flows · Webhooks for profile events

Can be scoped for

• Purchases and sign-ups at a kiosk can be recorded as events against the customer profile.

The API exposesCustomers and points balances · Activities that earn points · Rewards and redemptions · Webhooks for loyalty events

Can be scoped for

• A kiosk can show a member their points balance and award points for an in-store purchase.

The API exposesAudiences and members · Tags and segments · Campaigns · Transactional email · Webhooks for audience changes

Can be scoped for

• A newsletter sign-up at a kiosk can add the customer to an audience with consent recorded.

The API exposesReview invitations · Business reviews and ratings · Product reviews · Review summaries

Can be scoped for

• A review invitation can be sent after a kiosk purchase.
• Published reviews can be shown on in-store displays, within the terms of the review platform.

The API exposesSMS and messaging · Voice calls · Verification codes · Webhooks for delivery and replies

Can be scoped for

• An order-ready text can be sent when a kiosk order is prepared.
• A one-time code can confirm a telephone number entered at a kiosk.

The API exposesTransactional email · Templates · Contacts and lists · Webhooks for delivery and engagement

Can be scoped for

• Receipts and confirmations requested at a kiosk can be sent by email from a verified sending domain.

The API exposesSMS and messaging · Voice and video · Verification codes · Webhooks for delivery receipts

Can be scoped for

• Text notifications and one-time codes can be sent from kiosk software.

The API exposesTemplate and session messages · Media and interactive messages · Webhooks for incoming messages and delivery status

Can be scoped for

• Order updates can be sent by WhatsApp where the customer has opted in.
• A QR code on a kiosk or display can open a chat with the business.

The API exposesReviews and ratings · Loyalty points and rewards · Customers · Webhooks for loyalty and review events

Can be scoped for

• Product reviews can be shown beside items on a kiosk or display.
• In-store purchases can earn points in the same loyalty programme as online orders.

The API exposesAppointment types and calendars · Available dates and times · Appointments and clients · Webhooks for booking changes

Can be scoped for

• A reception kiosk can book the next available slot or check a client in for an existing appointment.

The API exposesEvents and schedules · Tickets and availability · Attachments and locations · Class passes

Can be scoped for

• A display can list the classes of the day and the places remaining.
• A kiosk can link to booking for a chosen session.

The API exposesEvent types and schedules · Availability · Bookings · Webhooks for booking events

Can be scoped for

• A kiosk can offer available appointment times and confirm a booking on the spot.

The API exposesEvent types · Scheduled events and invitees · Availability · Webhooks for bookings and cancellations

Can be scoped for

• A showroom kiosk can offer a follow-up appointment with a member of the sales team.

The API exposesEvents and ticket classes · Orders and attendees · Check-in status · Webhooks for orders and attendee changes

Can be scoped for

• A self-service kiosk can check attendees in from their ticket code and print a badge.
• A display can list forthcoming events and remaining tickets.

The API exposesBooking businesses and services · Staff availability · Appointments and customers

Can be scoped for

• A reception or service-desk kiosk can book or check in appointments held in Microsoft 365.

The API exposesClasses and schedules · Appointments · Clients and memberships · Sales and services

Can be scoped for

• A kiosk at the entrance can check members in to a class or sell a drop-in session.

The API exposesAvailability and reservations · Guest details · Restaurant information

Can be scoped for

• A host-stand or lobby kiosk can show availability or check a party in, subject to access being granted by the provider.

The API exposesLocations and lines · Tickets and visitor details · Calling and serving status · Webhooks and live events

Can be scoped for

• A kiosk can issue a place in the queue and a nearby display can call the next visitor.

The API exposesReservations and availability · Guest profiles · Waitlist entries

Can be scoped for

• Arrival kiosks can check guests in against their reservation, subject to access being granted by the provider.

The API exposesServices and providers · Available time slots · Bookings and clients · Notifications of booking changes

Can be scoped for

• A walk-in customer can book the next available slot at a kiosk.

The API exposesLocations and services · Visits, waitlist entries and bookings · Customers · Webhooks for visit events

Can be scoped for

• A kiosk can add a walk-in customer to a virtual queue and tell them the expected wait.

The API exposesListings and product data · Orders · Inventory held by Amazon and by the seller · Reports and notifications

Can be scoped for

• Stock shown on an in-store kiosk can take account of units committed to marketplace orders.

The API exposesOrders from connected channels · Menus and availability · Order status updates · Store opening status

Can be scoped for

• A kiosk can be added as another ordering channel so its orders follow the same route as delivery orders.

The API exposesOrders and status updates · Menus and item availability · Site opening status

Can be scoped for

• Item availability can be kept the same across kiosks, tills and the delivery menu.
• Collection displays can show delivery orders alongside kiosk orders.

The API exposesListings and inventory · Orders and fulfilment · Product catalogue data · Notifications of sales

Can be scoped for

• A retailer selling the same stock in a shop and on eBay can keep quantities aligned as kiosk sales are made.

The API exposesShop listings and inventory · Receipts and orders · Shop details

Can be scoped for

• A kiosk in the shop or market stall of a maker can show listings and keep quantities aligned with online sales.

The API exposesOrders and status updates · Menus and availability · Restaurant opening status

Can be scoped for

• Delivery orders can appear with kiosk orders on kitchen and collection displays.

The API exposesOrders from connected channels · Menus and item availability · Order status updates

Can be scoped for

• Kiosk orders can sit beside delivery orders in one preparation and collection view.

The API exposesOrder import · Label generation · Despatch status and tracking numbers

Can be scoped for

• An order placed at a kiosk for home delivery can be passed on for a label to be produced.

The API exposesOrders and shipments · Carriers and services · Labels and tracking · Webhooks for order and shipment events

Can be scoped for

• Kiosk orders for delivery can join the same despatch process as web orders.

The API exposesOrders and status updates · Menus and item availability · Store status and opening hours

Can be scoped for

• Menu and availability changes can be applied to kiosks and the delivery menu together.

The API exposesSign-in with passwords, codes or social accounts · User profiles and roles · Tokens using open standards · Logs and events

Can be scoped for

• Customer accounts used on a website can also be used to sign in at a kiosk.
• Staff access to kiosk administration can follow the sign-in rules of the organisation.

The API exposesVisitor entries and invitations · Locations and employees · Desk and room reservations · Webhooks for sign-in events

Can be scoped for

• A reception kiosk can sign visitors in, notify their host and print a badge.

The API exposesSign in with Google · Tokens using open standards · Basic profile details with consent

Can be scoped for

• Staff tools can use Google Workspace accounts for sign-in.
• Customers can sign in on their own phone after scanning a code shown on a kiosk.

The API exposesSign-in using open standards · Users, groups and roles · Administration interface · Events

Can be scoped for

• Kiosk and back-office applications can share one sign-in service kept within the infrastructure of the customer.

The API exposesSign-in and single sign-on · Users and groups · Application roles · Conditional access decisions

Can be scoped for

• Staff can sign in to kiosk administration with their work account.
• Staff-facing kiosks can show content according to group membership.

The API exposesSign-in and single sign-on · Users and groups · Application assignments · System log events

Can be scoped for

• Staff access to kiosk management can follow the sign-in and leaver rules already set in Okta.

The API exposesApplicants and checks · Document and facial verification · Verification reports · Webhooks for completed checks

Can be scoped for

• A kiosk with a camera and document scanner can capture what a check needs, subject to legal and privacy review.

The API exposesVerification sessions · Decision results · Document and facial checks · Webhooks for decisions

Can be scoped for

• Age or identity checks can be handed to the phone of the customer by QR code from a kiosk.

The API exposesFacial age estimation · Age verification results · Identity verification sessions · Digital identity sharing with consent

Can be scoped for

• Self-checkout and ordering kiosks can ask for an age check before age-restricted items are sold, subject to legal review.

The API exposesBases, tables and records · Views and fields · Attachments · Webhooks for record changes

Can be scoped for

• Content for information kiosks and displays can be edited by staff in a table.
• Enquiries can be logged as records for follow-up.

The API exposesStorage and content delivery · Databases and queues · Device messaging and management · Serverless functions

Can be scoped for

• Kiosk software, media storage and device telemetry can be hosted in a cloud account the customer owns.

The API exposesEvent collection from devices and servers · Reporting data · Audiences and conversions

Can be scoped for

• Kiosk journeys can be measured as events, such as screens viewed and orders completed, without personal data.

The API exposesData loading and streaming inserts · Queries · Datasets and tables · Scheduled exports

Can be scoped for

• Sales and usage events from a kiosk estate can be stored for analysis alongside other company data.

The API exposesStorage and hosting · Databases and messaging · Speech, translation and vision services · Serverless functions

Can be scoped for

• Kiosk back-end services can be hosted in a cloud project the customer owns.
• Speech and translation services can be assessed for accessible or multilingual kiosks.

The API exposesReading and writing cell ranges · Sheets and formatting · Change notifications through Google Drive

Can be scoped for

• Opening hours, offers or menu items can be edited in a sheet and shown on displays.
• Enquiries can be appended as rows for a small team.

The API exposesConnectors to data sources · Report and data source management · Embedded reports

Can be scoped for

• Reports on kiosk sales and usage can be built from data the kiosk software exports.

The API exposesEvent and page tracking · Reporting data · Goals and segments

Can be scoped for

• Screen views and completed journeys on kiosks can be measured on a server the customer controls.

The API exposesStorage and hosting · Databases and messaging · Device messaging and management · Speech, translation and vision services

Can be scoped for

• Kiosk back-end services can run in an Azure subscription the customer owns.

The API exposesDatasets and data refresh · Pushing rows to datasets · Reports and dashboards · Embedded reports

Can be scoped for

• Sales and usage data from kiosks can feed reports the business already uses.
• A dashboard can be shown on a back-office display.

The API exposesPages and blocks · Databases and their entries · Users and comments

Can be scoped for

• Information pages maintained in Notion can be published to an information kiosk.

The API exposesEvent collection · Statistics and breakdowns · Goals

Can be scoped for

• Kiosk usage can be measured as simple events without collecting personal data.

The API exposesData loading · Queries over a web interface · Continuous ingestion · Data sharing

Can be scoped for

• Transaction and usage data from kiosks can be loaded for analysis with the rest of the business data.

The API exposesData sources and extracts · Workbooks and views · Embedded dashboards · Webhooks for refresh events

Can be scoped for

• Kiosk data exported to the company warehouse can appear in existing dashboards.

The API exposesDesigns and folders · Exports to image, video and document formats · Assets and brand templates

Can be scoped for

• Artwork designed in Canva can be exported at the right size and published to displays.

The API exposesContent entries and assets · Content models · Localised content · Webhooks for publishing events

Can be scoped for

• The same content that feeds a website can be shown on information kiosks and displays.

The API exposesFiles and folders · Shared links · File change notifications

Can be scoped for

• Media dropped into a shared folder can be picked up and scheduled on displays.

The API exposesCalendars and events · Free and busy times · Notifications of event changes

Can be scoped for

• A meeting-room display can show the bookings of the room for the day.
• A lobby display can list the events of the day.

The API exposesFiles and folders · Sharing permissions · Change notifications · File export

Can be scoped for

• Images and video placed in a shared folder can be published to displays.

The API exposesInteractive and static maps · Place details and search · Directions and travel times · Address lookup

Can be scoped for

• A wayfinding kiosk can show directions from its own location to nearby places.
• Address entry at a kiosk can use address lookup to reduce typing.

The API exposesMedia and captions from the account · Comments and mentions · Account insights

Can be scoped for

• A display can show recent posts from the account of the business, within the terms of the platform.

The API exposesHourly and daily site-specific forecasts · Observations · Map images and model data

Can be scoped for

• Displays can show the local forecast.
• Content rules can change what is shown according to the weather.

The API exposesFiles and document libraries · Lists and site pages · Calendars and rooms · Change notifications

Can be scoped for

• News, notices and documents held in SharePoint can be shown on staff information displays.
• Meeting-room displays can show bookings from room calendars.

The API exposesLive departure and arrival boards · Timetables · Service disruption messages

Can be scoped for

• A display near a station, in a hotel or at a venue can show live departures from the nearest station.

The API exposesCurrent weather · Hourly and daily forecasts · Weather map layers · Air quality data

Can be scoped for

• Displays can show current conditions and a forecast for the site.

The API exposesMap tiles in several styles · Place name and address search · Geographic features

Can be scoped for

• Wayfinding and visitor information kiosks can use detailed British mapping.

The API exposesHeadlines, summaries and links · Publication dates · Media attachments

Can be scoped for

• Displays can show headlines from the news feed of the organisation.
• Third-party feeds can be shown where their terms allow public display.

The API exposesLive arrivals at stops and stations · Line status and disruption · Journey planning · Cycle hire availability

Can be scoped for

• A display in a London venue can show live departures from nearby stops and the status of nearby lines.

The API exposesVideos and folders · Playback links and embeds · Upload and replace · Live events

Can be scoped for

• Video managed in Vimeo can be played on kiosks and displays, with a local copy kept where connectivity is limited.

The API exposesConversion between three-word addresses and coordinates · Address suggestions · Map grid

Can be scoped for

• A wayfinding or visitor kiosk can accept or display a three-word address for an entrance or meeting point.

The API exposesPosts, pages and custom content types · Media library · Categories and tags · Users and comments

Can be scoped for

• News, events or product pages already published on a website can be reused on kiosks and displays.

The API exposesVideos, playlists and channels · Embedded player control · Live streams

Can be scoped for

• The videos of a channel can be played on displays using the embedded player, within the terms of the service.

The API exposesLabel templates and printing · Printer status · Connection over USB, network and Bluetooth

Can be scoped for

• A kiosk can print visitor badges, collection labels or product labels on demand.

The API exposesReceipt layout and printing · Printer and paper status · Cash drawer and customer display control

Can be scoped for

• A kiosk can print order tickets and receipts and warn staff when paper is low.

The API exposesText, barcode and image printing · Paper cut and cash drawer commands · Printer status requests

Can be scoped for

• Kiosk software can drive a wide range of receipt printers without a maker-specific kit.

The API exposesPublishing and subscribing to topics · Device status messages · Retained and last-will messages

Can be scoped for

• Sensors, door contacts and other devices can report to kiosk software.
• Kiosks can report their own health to a monitoring service.

The API exposesCard detection and removal · Reading card identifiers · Commands to the card or tag

Can be scoped for

• A kiosk can read a membership card, staff pass or tag to identify the user. Reading a tag is not taking a card payment.

The API exposesReceipt and label printing · Printer and paper status · Cash drawer and peripheral control · Cloud printing

Can be scoped for

• A kiosk can print order tickets and receipts, and kitchen printers can receive the same order.

The API exposesPrinters, scanners and scales · Cash drawers and customer displays · Device status events

Can be scoped for

• Peripherals that follow the standard can be swapped without rewriting the kiosk software.

The API exposesUSB device communication · Serial port communication · Human interface device reports

Can be scoped for

• A web-based kiosk application can use a printer, scanner or reader directly from the browser.

The API exposesBarcode scan data and scanner settings · Label and receipt printing · Device status and management

Can be scoped for

• A kiosk can scan product, ticket or membership barcodes and print labels or wristbands.