Skip to content

FousiFood Portal do Parceiro

Pull your iFood repasses and reviews into your systems

Read each store's repasses, the events of the Relatório de conciliação and its unanswered reviews from the iFood Portal do Parceiro with one API call each. Or have a workflow check Wednesday's repasses and send last week's conciliação to accounting.

Works with your own iFood Portal do Parceiro account. Fous is an independent product.

What you can build on the Portal do Parceiro

  • Get repasses

    Build this

    Reads the Painel Financeiro (financial dashboard) for one store: each repasse (payout), its status and how it was made up.

    Takes
    Store, from date, to date
    Returns
    Period, repasse date, status, sales, commission, online payment fee, plan fee, adjustments, net value
  • Get the reconciliation events for a period

    Build this

    Reads the Relatório de conciliação (reconciliation report) for one store and period: every financial event, with its value and whether it affects the repasse.

    Takes
    Store, from date, to date
    Returns
    Order number, date, event type, description, value, affects the repasse
  • Get reviews awaiting a reply

    Build this

    Reads the Avaliações e Comentários tab (reviews and comments) for one store and keeps the reviews that have no reply yet.

    Takes
    Store
    Returns
    Order number, review date, order rating, delivery rating, public or private, attributes, comment
  • Contest a cancelled order

    Build this

    Finds the order in Pedidos (orders), opens Ver detalhes, and when Contestar cancelamento is active, writes the justification and selects Abrir contestação.

    Takes
    Store, order number, justification
    Returns
    Order number, contest available, contest opened, status

Automate the Portal do Parceiro with a workflow

A workflow runs your methods as one process, with nobody at the screen. A schedule or a call from your own system starts it, the steps run in order, and the result arrives in your inbox or in the systems you already use.

  • Wednesday repasse check, every store

    Build this
    Starts
    Every Wednesday at 11:00
    Step 1
    For each store you name, get the repasses dated today.
    Step 2
    Keep the repasses with the failed status, and stop when there are none.
    Step 3
    Email you the list with store, period, net value and status.
  • Last week's conciliação, sent to accounting

    Build this
    Starts
    Every Monday at 8:00, after the Monday to Sunday period closes
    Step 1
    For each store, get the reconciliation events from last Monday to Sunday.
    Step 2
    Keep the events that affect the repasse.
    Step 3
    Post them, with order number, date, event type and value, to your accounting system's webhook.
  • New reviews to answer, posted to your team

    Build this
    Starts
    Every day at 9:00
    Step 1
    For each store, get the reviews awaiting a reply.
    Step 2
    Keep the reviews that were not there on the last run.
    Step 3
    Post each one, with ratings and comment, to your Slack webhook.

You can run a workflow by hand on every plan, Free included. Schedules and webhook triggers come with the paid plans, from $29 a month.

Once built, one call from your code

Once you have built a method, it is one POST to /v1/runs from your backend, or a tool an AI agent calls over MCP. This is what “Get repasses” would look like.

Example request
curl https://api.fous.com/v1/runs \
  -H "Authorization: Bearer $FOUS_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "method": "portal.ifood.com.br/get_repasses",
    "input": {
      "store": "Acme Burger, Pinheiros",
      "from": "2026-11-01",
      "to": "2026-11-18"
    }
  }'
Example response
{
  "status": "completed",
  "data": {
    "store": "Acme Burger, Pinheiros",
    "repasses": [
      {
        "period": "2026-10-05 to 2026-10-11",
        "repasse_date": "2026-11-11",
        "status": "confirmed",
        "sales": 18420.5,
        "commission": -2210.46,
        "online_payment_fee": -497.35,
        "plan_fee": -110,
        "adjustments": -64.9,
        "net_value": 15537.79,
        "currency": "BRL"
      }
    ],
    "count": 1
  }
}

An example with invented data, not a ready-made endpoint. The method exists in your organization once you build it, and its name, inputs and fields follow your request.

The Portal do Parceiro’s own options

iFood publishes a Merchant API on its developer portal, with modules for the merchant, catalog, orders, reviews, financial data and analytics. Production access goes through iFood's homologation, and the Financial module requires a company (CNPJ) account and its own homologation ticket. In the Portal do Parceiro itself you have the Painel Financeiro and the Relatório de conciliação.

OptionWhat it coversWhat it takes
iFood Merchant API, Financial moduleSales, financial events, settlements, anticipation and an on-demand reconciliation file, for an app that serves partner stores.A developer account with a CNPJ, an app tested in the test environment, a questionnaire and a review before production.
iFood Merchant API, operational modulesMerchant, Catalog, Order, Events, Logistics, Shipping and Review.A complete integration homologated by iFood. Read-only apps such as BI or dashboards are accepted only for Financial and Analytics.
Relatório de conciliaçãoEvery financial event of a period, such as sales, discounts and promotions, as the official spreadsheet for accounting.Your store's Portal do Parceiro account.
The Portal do Parceiro by handCardápio, opening hours, delivery area, sales history, repasses, reviews and cancellation contests, store by store.The email and password registered for your store.

Read on November 12, 2026: iFood Developer: Financial module homologation criteria, iFood para Parceiros: ciclo de repasse, iFood para Parceiros: como acessar o Portal do Parceiro.

Signing in to the Portal do Parceiro

The Portal do Parceiro signs you in at portal.ifood.com.br with the email and password registered for your store, entered one after the other. With Fous you sign in once through the Portal's own sign-in with your own account: the login is sealed with AES-256, code and AI agents never see it, and an expired session is signed back in.

Worth knowing

Weekly periods, repasses on Wednesdays
iFood closes sales in 7-day periods from Monday to Sunday and pays repasses on Wednesdays. On the standard plan, a closed period is paid 4 weeks later, so a Wednesday repasse covers a period that closed 4 weeks before.
A cancellation can be contested for 7 days
After 7 days from the cancellation, Contestar cancelamento is no longer available. iFood analyses a contest within 72 hours, and an accepted refund appears in the Reembolsos (refunds) tab within 48 hours.
5 days to answer a review
Customers have 7 days to review an order and the store has 5 days to reply. A reply can be edited for 10 minutes. Private reviews do not count in the rating but are visible in the Portal.
Orders arrive in the Gestor de Pedidos
Orders arrive in real time in the Gestor de Pedidos, not in the Portal do Parceiro. The Gestor de Pedidos must be open for the store to show as available.

More in Food service, restaurants and alcohol

Other industries: CommBiz, CAFS, RD e-Filing, MCA21, Airbnb hosting dashboard, IESS - Portal de Empleadores.

Frequently asked questions

Not the Portal itself, but iFood publishes a Merchant API for integrators. It covers catalog, orders, reviews, financial data and more, and every integration goes through iFood's homologation before production. The Financial module needs a company (CNPJ) developer account and its own homologation ticket.

In the Painel Financeiro of the Portal do Parceiro, which shows each repasse as scheduled, confirmed or failed. The Relatório de conciliação details every financial event, such as sales, discounts and promotions, and the deductions: the plan's commission, the online payment fee and the monthly fee when it applies.

7 days from the cancellation. You contest in Pedidos, under Ver detalhes, with Contestar cancelamento. A greyed-out button means the order cannot be contested. iFood analyses a contest within 72 hours.

5 days. The customer is notified of your reply and can revise the rating they gave, and you can edit a reply for 10 minutes. With Fous, a daily workflow can collect each store's unanswered reviews so nobody misses that window.

No. Fous is an independent product. You use it with your own Portal do Parceiro account, and a method reads and does only what that account can.

Put iFood Portal do Parceiro behind an API call

Describe one job in Studio and see the method it builds, with 100 credits a month and no credit card, or book a demo and bring the sites your team signs in to.

Read nextJust Eat Partner HubPedidosYa Partner PortalRappi AliadosCommBizHow methods workHow workflows run

Fous is an independent product: it is not affiliated with, endorsed by or sponsored by the operator of iFood Portal do Parceiro (iFood). The name is used only to say which system this page is about. Something here wrong or out of date? Write to legal@fous.com.