get_check_detail requires a unique_id. Where does that come from?

The unique_id for a check comes from the uniqueID field returned by search_checks. The typical workflow is to call search_checks first to find the checks you need, then pass the uniqueID values from those results to get_check_detail to retrieve full check data.

What date formats does Aloha accept for date_of_business?

Both search_checks and get_daily_ddv_reports accept date_of_business in either M/D/YYYY format (e.g. 7/4/2026) or YYYY-MM-DD format (e.g. 2026-07-04). get_daily_ddv_reports defaults to yesterday if date_of_business is omitted.

How do time_from and time_to work in search_checks?

time_from and time_to are integer time filters that Aloha's check search endpoint expects. Pass -1 for both to retrieve checks across the full business day without a time window restriction.

Aloha uses subdomains. How does Integuru handle the base URL?

The base URL is https:// .alohaenterprise.com/login.do. You configure your organization's specific subdomain once during Integuru setup; Integuru handles authentication automatically.

Back to Integrations

Restaurants & Food Service

Aloha

Integuru generates a production-ready HTTP API for Aloha, the enterprise restaurant POS platform. The integration covers 4 actions for store listing, check search, check detail retrieval, and daily DDV report retrieval, all carrying richer docs, enabling restaurant tech teams to automate POS data access programmatically.

4actions

https://<SUBDOMAIN>.alohaenterprise.com/login.do

Last reviewed: July 2026

Overview

Integuru's Aloha integration provides production-ready HTTP API access to Aloha, the enterprise restaurant POS platform at <SUBDOMAIN>.alohaenterprise.com, covering 4 actions: list_stores, search_checks, get_check_detail, and get_daily_ddv_reports. All 4 actions carry richer documentation. Integuru connects via direct HTTP requests rather than browser automation, so calls complete in under 3 seconds with a 99.9%+ success rate.

No public developer API. Aloha does not expose an official developer API for check and sales data. Restaurant tech teams and multi-unit operators that need POS transaction data or daily sales reports programmatically have had to rely on manual exports or fragile browser-based scripts.

The integration covers the core POS data surfaces: store roster via list_stores, check search via search_checks, individual check detail via get_check_detail, and daily DDV (Daily Detail View) report retrieval via get_daily_ddv_reports. Restaurant tech developers use these actions to pull sales data, reconcile POS records, and feed daily reporting pipelines. See the SpotOn integration or MarginEdge integration for other restaurant-tech integrations, or browse the full integrations catalogue.

Use Cases

Integuru's Aloha integration covers the POS data retrieval workflows that restaurant tech teams need to automate.

Store listing: Call list_stores with optional app_id (defaults to 2) to retrieve the list of Aloha stores for the authenticated account.
Check search: Call search_checks with optional store, company, date_of_business (M/D/YYYY or YYYY-MM-DD), check_number, time_from, time_to (use -1 for all-day), and filter to retrieve matching POS checks.
Check detail retrieval: Call get_check_detail with the required unique_id (from search_checks results) and optional show_id to retrieve full detail for a specific check.
Daily DDV report retrieval: Call get_daily_ddv_reports with required store_id and optional store_name and date_of_business (defaults to yesterday) to retrieve the daily DDV report for a store.

Setup Notes

Integuru's Aloha integration authenticates against https://<SUBDOMAIN>.alohaenterprise.com/login.do. Configure your subdomain and credentials once during Integuru setup; Integuru handles session management automatically.

get_check_detail requires unique_id; all other parameters are optional. get_daily_ddv_reports requires store_id; store_name and date_of_business are optional (the latter defaults to yesterday). All parameters in list_stores and search_checks are optional.

Richer documentation for all 4 actions is available via the Integuru dashboard after setup.

Available Actions

Click an action to expand its parameters

Don't see the action you need?

The actions above cover the most common Aloha integration patterns, but they're not the full picture. Integuru can build additional workflows for any capability the platform exposes. Our Managed Service handles scoping, building, and maintaining custom actions on your behalf, so just let us know what you need.

Managed Service Get started free

Overview

Use Cases

Setup Notes

Available Actions

Frequently Asked Questions