What Demander fetches from Meu ERP Online
Fetch uses the Meu ERP Online public SQL API (api/consulta/sql/v1), with pagination (limit 100 records per page).
Each active table in Tabelas de Integração Meu ERP Online defines:
- the SQL query in the ERP
- the Demander layout file name (numeric prefix)
- the execution order
Demander formats the response in column order and sends it to the standard importer (positional webservice).
How to build and test queries: Integration setup.
Common layouts
Section titled “Common layouts”The exact list depends on what the company registered. Typical deployments include:
| File name (example) | Content |
|---|---|
02_VENDEDORES |
Sellers |
03_CIDADES |
Cities |
06_FORMAPAGAMENTO |
Payment methods |
09_LISTASPRECO |
Price lists |
13_PRECO_PRODUTO |
Product prices |
15_PRODUTO |
Products |
18_CLIENTES |
Customers |
19_TITULOS / 19_Titulos_Financeiros |
Financial titles |
22_Status de Pedidos |
Order status updates |
Some companies split “full” and “changed” sets (e.g. 18_CLIENTES and 18_CLIENTES_Alterados) to reduce automatic-run volume.
Query rules
Section titled “Query rules”SELECTorder is the layout order. Aliases only help reading the result in Testar query.- The API returns keys in lowercase; that does not change import.
- Tables blocked in company settings (do not import from ERP) are skipped on fetch.
- Orders with items use the special order-layout flow; the items table alone is not imported in isolation.
Fetch logs
Section titled “Fetch logs”Every run creates a record in Logs de integração Meu ERP Online, type Busca. The detail shows URL, request, response, and failures per table.