Silverware POS API

Does Silverware POS have a public API?

Silverware exposes an API to integration partners, with an access token and cloud address handed out through a Silverware representative per location, and no self-serve developer portal. An operator's own team therefore cannot pull last night's register summary without a partner arrangement. Integuru generates a production-ready HTTP API for Silverware POS from your own reporting login at reports.silverwarepos.com, with 12 verified actions across sales, registers, voids, discounts, the menu and any named store report.

What you can do with the Silverware POS API

A hotel food and beverage director runs the same report pack every morning across the restaurant, the bar and banquets: daily totals, register summary, top items, voids. Every action takes a required date_from and date_to, optional time_from and time_to to isolate a service, and a location scope.

Sales and totals

• get_sales and get_sales_analysis return sales and the analysed breakdown; get_daily_totals returns the day's totals per venue.
• get_top_items returns best sellers for the window.

Registers, voids and discounts

• get_register_summary, get_register_summary_extended and get_register_detail move from a summary to line-level register activity, the last with row_offset for paging.
• get_voids and get_discounts return the exception reports a controller reviews before posting the day.

Menu and everything else

• get_menu returns the menu configuration for store_ids in the window.
• generate_store_report runs any named report the portal offers, with job_id to re-fetch one already generated.
• list_venues returns the venue identifiers.

Who uses this

Hotel groups with Silverware in food and beverage outlets post get_daily_totals and get_register_summary per outlet into their property accounting each morning. Restaurant groups running several POS brands consolidate get_sales here with the same day's figures from the Heartland, SmartTab and Square pages. Inventory tools read get_top_items and get_menu to keep recipe mapping current, and controllers building a period-end pack use generate_store_report for the reports no dedicated action covers. The restaurants industry page covers the daily close and multi-location reporting together.

Setup notes

Integuru authenticates against reports.silverwarepos.com with your Silverware reporting user. Call list_venues first and choose one location parameter style (location, location_ids, locations or store_ids) for the whole integration. date_from and date_to are required everywhere; add time_from and time_to for a service window. output_format is optional and available on every report.

Get started

Install the CLI and connect your Silverware POS login:

npm install -g integuru

Or sign in at app.integuru.com, add Silverware POS, and call the same 12 actions from the dashboard. For labor reports or menu writes, the Managed Service scopes and builds the action against your account.