Indy API

Does Indy have a public API?

Indy exposes its reporting through the signed-in admin app at admin.indy.systems rather than a documented developer API. Integuru's 20 verified actions give your admin login direct HTTP access to that reporting: sales, orders, payments, cash management, discounts, voids and refunds, all scoped by site, with no browser or export step in between.

What you can do with the Indy API

Sales reporting. sales_summary and daily_sales_summary cover a single date or a start_date to end_date range. The daily report ranks top items (top_n, default 20) and by default keeps food and beverage classes while dropping booking fees, gift cards, membership intervals and tips, with item_classes and exclude_item_classes to override. item_sales_summary, employee_sales_summary (by employee_id and site_id) and marty_fnb_sales_by_channel slice the same period by item, staff member and sales channel. run_reconciliation_summary produces the close-out figures for one site_id over a range.

Orders and payments. list_orders filters by date range, state (including canceled, partially_canceled and partially_refunded), sales_channel, employee_id and showing_id, and with include_item_details on by default splits each line into item name, menu price and modifiers. list_payments filters by disputed, transfer_id and site.

Cash management. list_cash_sessions, list_cash_counts (count_type of user or cash-tray), list_cash_adjustments and list_cash_deposits share one shape: a date range, register_station_id or user_id filters, and a limit of 500 with offset for paging.

Discounts, voids and refunds. list_discounts, list_fnb_employee_discounts, list_voids, fnb_voids and fnb_refunds return the exceptions an auditor asks about, per site or across every site with show_all_sites.

Reference. list_sites returns the locations and the numeric IDs every other action wants, list_users returns staff with user_role and per-site filters, and list_news_items reads the admin news feed.

Who uses this

Finance teams closing multi-site venues pull run_reconciliation_summary and list_cash_deposits per site each morning instead of exporting reports by hand. Loss-prevention reviews combine list_voids, fnb_refunds and list_fnb_employee_discounts by employee over the same range. Operators who route delivery orders through Checkmate or run other locations on SpotOn get the same response shape across all of them, and the restaurants industry page covers the workflow from sales to payroll.

Setup notes

Integuru authenticates against admin.indy.systems with your Indy admin user. Call list_sites first; passing site_id on a report applies the site switch for you, and an unknown site name returns a 400 with the list of valid locations. Dates are YYYY-MM-DD, with MM/DD/YYYY and YYYY/MM/DD normalised on most range parameters. list_payments and list_users default to 10 results, so raise limit for a full pull.

Get started

Install the CLI and connect your Indy login:

npm install -g integuru

Or sign in at app.integuru.com and add Indy. To bring ticketing, showings or menu management into the same workflow, the Managed Service scopes and builds those actions against your account.