Skip to main content
Mogo Gourmet is a point of sale (POS) and management system for restaurants, bars and food delivery. This connector reads your establishment’s data through the Mogo API and brings every payment (your sales, with the items paid), the menu (products and product groups), tables and tabs, payment types, couriers and open cash registers.
The connector only reads data. It never creates, changes or deletes anything in Mogo.

Before you start

Mogo opens its API to an establishment only after it approves the integration with Nekt. Ask Mogo support to enable the API integration with Nekt for your establishment, and to send you these three values:
  • Client Token (Mogo may call it tokenCliente).
  • Software House Token (Mogo may call it token_sh).
  • Database Name (Mogo may call it dbname).
Mogo often sends the three values together, as a single “full token” text in the format <Client Token>token_sh=<Software House Token>dbname=<Database Name>, sometimes starting with Token . Split it into the three fields like this: Full token sent by Mogo: Token CLIENT_TOKENtoken_sh=SOFTWARE_HOUSE_TOKENdbname=DATABASE_NAME Do not include the markers token_sh= and dbname= themselves in any field. Mogo generates these values for each server, so each establishment has its own. Also check with Mogo where your Mogo runs:
  • In Mogo’s cloud (app.mogogourmet.com.br): nothing else is needed. In the source, choose Mogo’s cloud in Where Mogo Runs.
  • On your establishment’s own server (on-premise; Mogo may call it an offline installation): choose Establishment’s own server in Where Mogo Runs. You also need the address of the Mogo API on that server, with its port, for example https://mogo.yourcompany.com.br:1690. Ask Mogo support or your IT team for it.
If Mogo runs on your own server, the server must be reachable from the internet and its firewall must accept connections from Nekt’s IP addresses: 34.24.209.97, 34.74.81.117 and 34.138.230.39. These are the addresses of Nekt Express. If your Nekt workspace runs on your own cloud account (GCP or AWS), ask Nekt support for the addresses to allow.

Configuring Mogo Gourmet as a Source

In the Sources tab, click on the “Add source” button located on the top right of your screen. Then, select the Mogo Gourmet option from the list of connectors. Click Next and you’ll be prompted to add your access.

1. Add account access

The following configurations are available:
  • Client Token: the integration token of your establishment, given by Mogo. If Mogo sent a single full token, see how to split it.
  • Software House Token: the integration token Mogo generated for this establishment’s integration with Nekt.
  • Database Name: the name of your establishment’s database in Mogo, given by Mogo together with the tokens.
  • Where Mogo Runs: choose where your establishment’s Mogo is installed (see Before you start).
    • Mogo’s cloud (app.mogogourmet.com.br), the default: nothing else to fill in. The two fields below do not appear.
    • Establishment’s own server (on-premise): the API Address field appears, and the Verify SSL Certificate option appears in the advanced settings.
  • API Address (only for the establishment’s own server, required there): the address of the Mogo API on that server, with the port, for example http://mogo.yourcompany.com.br:1690 or https://mogo.yourcompany.com.br:1692. Use only the address, without the database name, a path, user, password or parameters.
  • Start Date: the earliest payment and order date synced. The other tables (products, tables, payment types and so on) are always read in full.
  • Verify SSL Certificate (advanced, only for the establishment’s own server, on by default): keep it on. Turn it off only when the API Address is https and that server uses a self-signed certificate. With it off, the connection stays encrypted, but the server’s identity is not checked. Sources on Mogo’s cloud always verify the certificate.
One source reads one establishment (one Mogo database). If you have more than one establishment, create one source for each, with its own tokens, Database Name and, on your own servers, its own API Address. On one server, each database usually has its own port.
Prefer an https address. An http address works, but the tokens and your data travel between the Mogo server and Nekt without encryption, and each sync log shows a warning. If your server only answers http, ask your IT team or Mogo support to enable https.
Once you’re done, click Next.

2. Select streams

Choose which data streams you want to sync. For faster extractions, select only the streams that are relevant to your analysis. You can select entire groups of streams or pick specific ones.
Tip: The stream can be found more easily by typing its name.
Orders and Product subgroups are not selected by default (see Available streams). Select them only if they apply to your establishment. Select the streams and click Next.

3. Configure data streams

Customize how you want your data to appear in your catalog. Select the desired layer where the data will be placed, a folder to organize it inside the layer, a name for each table (which will effectively contain the fetched data) and the type of sync.
  • Layer: choose between the existing layers on your catalog. This is where you will find your new extracted tables as the extraction runs successfully.
  • Folder: a folder can be created inside the selected layer to group all tables being created from this new data source.
  • Table name: we suggest a name, but feel free to customize it. You have the option to add a prefix to all tables at once and make this process faster!
  • Sync Type: keep the suggested type. Payments and Orders are Incremental: each sync reads only the last days and merges them into the table. The other tables are Full table: Mogo gives no change date for them, so each sync reads them whole and replaces the table.
Once you are done configuring, click Next.

4. Configure data source

Describe your data source for easy identification within your organization, not exceeding 140 characters. To define your Trigger, consider how often you want data to be extracted from this source. This decision usually depends on how frequently you need the new table data updated (every day, once a week, or only at specific times). Payments are read incrementally, so an hourly or daily sync works well. Optionally, you can determine when to execute an Additional Full Sync. A weekly full sync is recommended: it rebuilds the Payments table with Mogo’s current report, which removes payments deleted or reversed in Mogo (see Implementation Notes). Optionally, you can configure Delta Log Retention and determine for how long we should store old states of this table as it gets updated. Read more about this resource here. Once you are ready, click Next to finalize the setup.

5. Check your new source

You can view your new source on the Sources page. If needed, manually trigger the source extraction by clicking on the arrow button. Once executed, your data will appear in your Catalog.
For you to be able to see it on your Catalog, you need at least one successful source run.

Streams and Fields

Available streams

The table below lists every stream, its slug (the exact identifier to pass when creating the source via API) and a short description. Use Payments for your sales. Join payments.payment_type with payment_types.description, and products.group_id with product_groups.id.

Fields by stream

Fields marked String (JSON) hold a nested list as JSON text; use your warehouse’s JSON functions to read them. Dates and times are the establishment’s local date and time, as Mogo records them, with no time zone. Amounts are in BRL.
The establishment (restaurant) of the source, from its Mogo database.Table: establishment · Primary key: id · Sync: Full table
Products on the menu, with price, group and subgroup.Table: products · Primary key: id · Sync: Full table
Groups that organize the products on the menu.Table: product_groups · Primary key: id · Sync: Full table
Subgroups inside the product groups. Not selected by default: Mogo’s API currently answers this table with an error. If you select it, it shows as failed with Mogo’s message until Mogo fixes it.Table: product_subgroups · Primary key: id · Sync: Full table
Payment types accepted by the establishment and the card brands of each one.Table: payment_types · Primary key: id · Sync: Full table
Active delivery couriers. The table is empty when the establishment has no active courier.Table: couriers · Primary key: id · Sync: Full table
Tables of the restaurant and their situation when the sync ran.Table: tables · Primary key: id · Sync: Full table
Every tab (comanda or card) of the establishment and its situation when the sync ran.Table: tabs · Primary key: tab_id · Sync: Full table
Cash registers that were open when the sync ran. The table is empty when no cash register is open. Mogo does not list cash registers open for more than 2 days.Table: open_cash_registers · Primary key: cash_register, employee_id, opened_on · Sync: Full table
Order headers (one row per order, without items), by order date. Not selected by default: Mogo’s order search returns only orders created through Mogo’s API or integrations, never orders typed in the point of sale. Select it only if your establishment takes orders through an integration. Use Payments for every sale.Table: orders · Primary key: id · Sync: Incremental (order_date)
Every payment from Mogo’s payment report, by payment date, with the items paid. This is the table of your sales.Table: payments · Primary key: payment_key · Sync: Incremental (payment_date)

Implementation Notes

Data Quality Considerations

  • Payments is the table of your sales. Mogo’s order search (the Orders table) returns only orders created through Mogo’s API or integrations, so most establishments get no orders there. Every sale made in the point of sale is in Payments.
  • How payments and orders stay up to date. They are read day by day, by the local date of the payment or order. Each sync reads the last 3 days again, so late payments and corrections are picked up. Orders still open are read again on the next syncs until they are closed, for up to 30 days.
  • Long first syncs are saved in steps of 30 days. If a first sync over a long period stops with an error, the days already read are kept and the next sync continues from there.
  • Payments have no id in Mogo. Nekt builds the payment_key column from the order and the payment date and time. A payment corrected in Mogo within the last 3 days (a different payment type, amount, table or tab) is updated in place.
  • A payment deleted or reversed in Mogo stays in the Payments table, because Mogo’s report gives no signal of removed payments. The same happens to the old row of a payment whose time was changed in Mogo. A full sync rebuilds the table with Mogo’s current report; schedule a weekly Additional Full Sync to keep it in line.
  • Orders changed after 3 days are not updated (for example, a paid order cancelled a week later), except orders still open. A full sync updates them.
  • Product subgroups is not selected by default because Mogo’s API currently answers it with an error. If you select it, it shows as failed with Mogo’s message until Mogo fixes it. The other tables keep syncing.
  • Open cash registers: Mogo does not list cash registers that have been open for more than 2 days. When that happens, the sync log shows Mogo’s notice.
  • Permissions: each table needs Mogo to allow it for your establishment’s integration. If Mogo refuses one of them, that table is skipped and not updated, the other tables keep syncing, and the sync log says which table was skipped.
  • Full table tables are never half updated. The connector reads all the data of a full table table before writing any of it. If Mogo fails while it is read, nothing of that table is sent and the sync shows it as failed. On GCP (BigQuery) the table keeps its previous content; on AWS, a full table table whose stream failed may be emptied by the load step until the next successful sync.

API Limits & Performance

  • Mogo does not publish a request limit. The connector waits a quarter of a second between requests and, when Mogo asks it to slow down, waits and tells you in the sync log.
  • Payments and orders are read one day per request. The first sync makes one request per day since the Start Date for each of these tables (about 365 requests for one year), so choose a Start Date that keeps it manageable.

Troubleshooting

Skills for agents

Download Mogo Gourmet skills file

Mogo Gourmet connector documentation as plain markdown, for use in AI agent contexts.