Back to Integrations
Restaurants & Food ServiceLive · 32 actions

Owner API

Integuru generates a production-ready HTTP API for Owner, the online ordering and marketing platform built for restaurants, for operators and the analytics, accounting and marketing tools that read its dashboard. 32 verified actions cover total sales, orders and average order value, item sales and product mix, payments, payouts, taxes, tips and fees, coupons and gift cards, labor and cash drawers, customers, subscribers, reviews, website visitors, marketing attribution and order conversion, plus brands, channels and locations.

npm install -g integuru
Backed byY Combinator100 API calls/month free

32

Verified actions live today

<3 sec

Response latency per call

99.9%+

Reliability rate on generated APIs

24/7

On-call maintenance on Production plans

Integration facts

Authenticates against
https://dashboard.owner.com/
Authentication
Login flows, including 2FA, handled by Integuru using your own Owner credentials.
Approach
Direct HTTP requests, with no browser automation or RPA involved.

Endpoints

Available actions

Click an action to expand its parameters

Don't see the action you need?

The actions above cover the most common Owner 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.

Guide

Owner integration guide

Does Owner have a public API?

Owner.com has no API. There is no developer portal, no API reference, no self-serve key and no webhook surface, and its POS and payment connections are set up by its own onboarding team. Integuru generates a production-ready HTTP API for Owner from your own dashboard login, with 32 verified actions covering every report the dashboard exposes: sales, product mix, payments and payouts, coupons and gift cards, labor and cash, customers, reviews, traffic and attribution.

What you can do with the Owner API

An operator who moved online ordering to Owner reviews three things weekly: what sold and through which channel, what the payout will be after tips, fees and taxes, and whether marketing is bringing in new customers. The actions cover each of those views for a start and end range, most with an optional unit for daily, weekly or monthly rows and an optional location_id.

Sales and product mix

  • get_total_sales, get_total_orders and get_average_order_value return the headline series.
  • get_item_sales (with channel_ids, sort and top_n), get_product_mix, get_sales_by_category and get_option_group_sales break sales down by item, mix, category and modifier group.
  • get_explore_orders and explore_customers return order and customer lists for deeper analysis, the latter paginated with page and limit.

Money in and money out

  • get_payments_by_type, get_payouts, get_settled_tips_and_fees, get_tips and get_taxes reconcile what customers paid to what reached the bank.
  • get_coupon_usage, get_coupon_breakdown, get_gift_card_purchases and get_gift_card_charges track promotions and stored value; get_third_party_savings reports savings against marketplace commissions.

Operations

  • get_labor (with granularity) and get_cash_drawer_history (with station_id) require a location_id and a start_date to end_date range.
  • get_print_shop_performance returns print-shop performance for a date range.

Guests and marketing

  • get_customers, get_subscribers, get_reviews, get_website_visitors, get_sources, get_marketing_attribution and get_order_conversion cover the funnel from visit to repeat order, all per location_id.
  • list_brands, list_locations and list_channels return the ids the reports accept.

Who uses this

Restaurant accounting tools pull get_payouts, get_settled_tips_and_fees and get_taxes on the payout cadence and post them beside the in-store figures from the Square or Heartland pages, so online and in-store revenue reconcile in one ledger. Multi-brand operators loop list_brands and list_locations and pull get_total_sales with unit set to weekly into the same warehouse as their Restaurant365 P&L. Marketing analytics tools compare get_marketing_attribution and get_order_conversion against ad spend by location, and guest platforms sync get_customers and get_reviews alongside reservation data from the Tock page. The restaurants industry page covers online ordering, loyalty and guest engagement together.

Setup notes

Integuru authenticates against dashboard.owner.com with your Owner login. Call list_locations and list_channels first. Watch the two parameter styles: start and end with optional location_id and unit on the sales and finance reports, start_date and end_date with required location_id on the customer, marketing, labor and cash reports. Dates are YYYY-MM-DD in both.

Get started

Install the CLI and connect your Owner login:

npm install -g integuru

Or sign in at app.integuru.com, add Owner, and call the same 32 actions from the dashboard. For menu edits, order status changes or other write actions, the Managed Service scopes and builds them against your account.

Guides in Restaurants & Food Service

Platform API guides in this vertical

Platforms available to request, not yet live

Good to know

Before you start

Can I use it today?
Yes. Every action listed above has been verified against live Owner traffic. Install the CLI or sign in at app.integuru.com, connect your Owner account, and start calling the endpoints.
What if Owner changes or breaks?
On Production plans the Integuru team is on call around the clock, with auth auto-healing included, so target-platform changes get fixed by Integuru rather than by your engineers.
What does it cost?
Start on the Free plan at $0/month with 100 API calls/month. Production starts at $499/month with 24/7 on-call maintenance and auth auto-healing.

FAQ

Frequently asked questions