Wisk API

Does Wisk have a public API?

WISK integrates with POS and accounting systems through its own connectors and does not publish a self-serve developer API for venue data. A bar operator cannot generate a key and pull last night's count. Integuru generates a production-ready HTTP API for Wisk from your own login, with 9 verified actions across venues, inventory sessions, intakes, purchase orders, items, recipes and distributors, three of them with change-feed cursors for cheap incremental sync.

What you can do with the Wisk API

A beverage director closing the week needs three numbers per venue: what was counted, what came in, and what is on order. The actions return each, plus the catalogue those numbers reference.

Counts and purchases

• wisk_inventories returns the newest inventory sessions for a venue_id, count at a time (default 10), with exclude_archived to skip archived sessions.
• wisk_intakes returns purchase movements for a venue, filtered by inserted_date_start and inserted_date_end, defaulting operation_type to intake and paginating 50 per page.
• wisk_intake_detail returns the line items on one movement given its movement_id.
• wisk_purchase_orders returns open and past purchase orders, paginated.

Catalogue with change feeds

• wisk_items, wisk_recipes and wisk_distributors return the item catalogue, subrecipes and batches, and vendors for a venue. Each accepts sequence_id: 0 for the full set, or the next_sequence_id from a previous response for changes only.

Venues

• list_venues and wisk_venues return the venues on the account, including the opaque venue_id string every other action requires.

Who uses this

Multi-venue bar groups run wisk_inventories per venue after each count and reconcile the result against sales from their POS pages, such as SmartTab or Silverware POS. Food-cost platforms sync wisk_items and wisk_recipes nightly with sequence_id, which keeps a 4,000-item bar catalogue current without a full pull. Purchasing tools match wisk_intake_detail lines against the distributor invoices they pulled from the US Foods page. The restaurants industry page covers inventory and purchasing together.

Setup notes

Integuru calls the same internal WISK API the web app uses, authenticated with your WISK user. Resolve venue_id from list_venues and treat it as an opaque string. For the three change-feed actions, persist next_sequence_id per venue and per action.

Intake date filters are YYYY-MM-DD, applied client-side, and a reversed range returns 400. Pagination on wisk_intakes and wisk_purchase_orders is local to the result set, 1-based, 50 per page.

Get started

Install the CLI and connect your Wisk login:

npm install -g integuru

Or sign in at app.integuru.com, add Wisk, and call the same 9 actions from the dashboard. For variance reports or count submission, the Managed Service scopes and builds the action against your account.