iFood para Entregadores icon

iFood para Entregadores — private driver-finance data API

iFood Delivery de Comida e Mercado · Food Delivery

iFood para Entregadores is the courier app from iFood Delivery de Comida e Mercado, the company behind Brazil's largest food- and grocery-delivery network, and it is where the platform's delivery partners manage the money side of their work. Couriers sign in on their own phone with a password, a one-time code or biometrics, then follow what they earn on a weekly earnings screen that totals their per-delivery entries over any date range and breaks them down day by day. The 'Meus Repasses' screen lists every consolidated payout, filterable by period and payment type, and opens into a detail view showing what each transfer paid, the fee taken and when it settled. A wallet screen shows the available and pending balance next to the Brazilian bank account that receives the money, and an early-payment (antecipação) screen lets couriers bring pending receivables forward, spelling out the fee, the minimum and maximum amounts, how often it pays out and how many daily and monthly requests are still available. Published for Brazil, the app serves the couriers who carry restaurant and supermarket orders for iFood, and it competes for their time with Rappi's Soy Rappi, Didi's 99Food, relaunched in Brazil in 2025, and Meituan's Keeta, which entered the Brazilian market the same year, while parcel apps such as Loggi Entregador and Lalamove are often run alongside it.

Per-delivery billing entries are where the courier ledger starts: each completed iFood delivery books one, and over any requested date range they roll up into a weeklyAmount total and a weeklyEarnings series carrying a date and amount for each day. Settled money then appears as consolidated payout records — each with an id, the settlement period, paymentDate and paymentTime, a paymentType such as weekly, a status such as paid, the payout amount and the feeAmount deducted — delivered as a period summary plus a paged data list and readable one payout at a time.

Next to that ledger sits the courier's wallet: an available-and-pending balance and the registered Brazilian payout account, described by bankCode, bankName, branchNumber, accountNumber with its accountDigit, accountType and the account holder's ownerDocument, returned masked. The early-payment side adds the receivables-anticipation plan: its name, the feeAmount charged, the minAmount and maxAmount a courier can bring forward, the paymentFrequency, and requested versus available counters that track the daily and monthly request limits. The driverId and userUuid issued at sign-in key every one of these records to a single courier, so payouts, earnings, balance and anticipation line up driver by driver.

Three kinds of products are built on this ledger. Accounting tools pull the payout history and per-payout detail nightly and match paymentDate, amount and feeAmount against bank statements so a courier's books close themselves. Fleet operators aggregate weekly amounts, billing entries and daily breakdowns across their drivers to rank productivity and forecast the week's cash-out. Lending products read the anticipation plan's fee, limits and paymentFrequency together with the wallet balance to pre-approve drivers for early payout on their receivables. openData Studio turns this iFood courier-finance data into callable open data, so reconciliation, earnings-dashboard and early-payment integrations can be built on it directly.

Screenshots

  • iFood para Entregadores screenshot 1
  • iFood para Entregadores screenshot 2
  • iFood para Entregadores screenshot 3
  • iFood para Entregadores screenshot 4
  • iFood para Entregadores screenshot 5
  • iFood para Entregadores screenshot 6
  • iFood para Entregadores screenshot 7

API surface

The endpoints and request/response examples below are reconstructed from the app's interface — illustrative, not a live capture.

  • OAuth2 driver token grant

    POST /v1/identity/session openfinance

    Authenticates a courier (password / otp / biometric / refresh grants) and returns the Bearer token plus driverId used by every other finance endpoint.

    Auth: None (issues tokens). Form-encoded body; device and installation headers identify the courier's handset.

    • accessToken
    • tokenType
    • refreshToken
    • expiresIn
    • userUuid
    • tenant
    • driverId
    • challengeType
    • factors
    POST /v1/identity/session HTTP/1.1
    Content-Type: application/x-www-form-urlencoded
    X-Device-Id: 3f2b8c1d-9a1e-4c2b
    X-Installation-Id: 7a91f0e2-55c1
    
    application=driver-app&username=11987654321&password=******
    {
      "accessToken": "eyJhbGciOi...",
      "tokenType": "Bearer",
      "refreshToken": "d8f1c2...",
      "expiresIn": 3600,
      "userUuid": "9b0e12f4-...",
      "tenant": "IFood",
      "driverId": "a41c9e02-..."
    }
  • List consolidated payouts

    GET /v1/payouts/history openfinance

    Returns the driver's consolidated payout history (summary + list) for a period, payment type and page — the core 'Meus Repasses' feed.

    Auth: Bearer accessToken from /v1/identity/session

    • id
    • paymentDate
    • period
    • paymentTime
    • paymentType
    • status
    • amount
    • feeAmount
    • summary
    • data
    GET /v1/payouts/history?period=2026-08&paymentType=WEEKLY&page=0&size=20 HTTP/1.1
    Authorization: Bearer eyJhbGciOi...
    {
      "summary": {"id": "sum", "paymentDate": "2026-08-31", "paymentType": "WEEKLY", "status": "PAID", "amount": 128540, "feeAmount": 0},
      "data": [
        {"id": "pay_01H...", "paymentDate": "2026-08-24", "period": {"start": "2026-08-18", "end": "2026-08-24"}, "paymentTime": "14:02:11", "paymentType": "WEEKLY", "status": "PAID", "amount": 64210, "feeAmount": 0}
      ]
    }
  • Get payout detail

    GET /v1/payouts/{payoutId} openfinance

    Reads a single payout's full detail (amount, fee, period, status) for the payout-detail screen.

    Auth: Bearer accessToken from /v1/identity/session

    • id
    • paymentDate
    • period
    • paymentTime
    • paymentType
    • status
    • amount
    • feeAmount
    GET /v1/payouts/pay_01H... HTTP/1.1
    Authorization: Bearer eyJhbGciOi...
    {
      "id": "pay_01H...",
      "paymentDate": "2026-08-24",
      "period": {"start": "2026-08-18", "end": "2026-08-24"},
      "paymentTime": "14:02:11",
      "paymentType": "WEEKLY",
      "status": "PAID",
      "amount": 64210,
      "feeAmount": 0
    }
  • Get billing-entry earnings summary

    GET /v1/earnings/summary openfinance

    Aggregates the driver's per-delivery billing entries into an earnings total over a date range.

    Auth: Bearer accessToken from /v1/identity/session

    • weeklyAmount
    • weeklyEarnings
    • amount
    • date
    GET /v1/earnings/summary?startDate=2026-08-01&endDate=2026-08-31 HTTP/1.1
    Authorization: Bearer eyJhbGciOi...
    {
      "weeklyAmount": 128540,
      "weeklyEarnings": [
        {"date": "2026-08-24", "amount": 64210, "entriesCount": 31}
      ]
    }
  • Get balance and payments

    GET /v1/wallet openfinance

    Reads the courier's current balance / payments list together with the registered Brazilian payout bank account.

    Auth: Bearer accessToken from /v1/identity/session

    • balance
    • accountType
    • accountNumber
    • accountDigit
    • branchNumber
    • bankCode
    • bankName
    • ownerDocument
    GET /v1/wallet HTTP/1.1
    Authorization: Bearer eyJhbGciOi...
    {
      "balance": {"available": 81240, "pending": 17300},
      "bankAccount": {"accountType": "CHECKING", "accountNumber": "00123456", "accountDigit": "7", "branchNumber": "0001", "bankCode": "341", "bankName": "Itaú", "ownerDocument": "123.***.***-45"}
    }
  • Get receivables anticipation plan

    GET /v1/advance-pay/plan openfinance

    Exposes the driver's early-payment (receivables anticipation) plan: fee, min/max amounts, frequency, and daily/monthly request counters. Failures map to a small set of payment error codes.

    Auth: Bearer accessToken from /v1/identity/session

    • name
    • feeAmount
    • minAmount
    • maxAmount
    • paymentFrequency
    • requested
    • available
    GET /v1/advance-pay/plan HTTP/1.1
    Authorization: Bearer eyJhbGciOi...
    {
      "name": "Antecipação Semanal",
      "feeAmount": 199,
      "minAmount": 5000,
      "maxAmount": 250000,
      "paymentFrequency": "WEEKLY",
      "requested": {"count": 1},
      "available": {"count": 3}
    }

Data categories

  • payouts
  • earnings
  • balances
  • payments
  • bank-accounts
  • receivables-anticipation
  • auth-tokens

Where teams use this data

  • Gig-work payout reconciliation

    Accounting tools pull the consolidated payout history and per-payout detail nightly, matching payment dates, amounts and fee amounts against bank statements so a courier's books close themselves.

  • Fleet earnings dashboards

    Fleet operators aggregate the weekly earnings summary across their drivers — weekly amounts, billing entries and daily breakdowns — to rank productivity and forecast cash-out for the week.

  • Receivables anticipation offers

    Lending products read the advance-pay plan (fee, min/max amount, payment frequency) together with the wallet balance to pre-approve drivers for early payout on their receivables.

Frequently asked questions

How does the iFood driver app authenticate?

Via a form-encoded token grant at POST /v1/identity/session, sending device and installation identifiers and receiving an access token, refresh token, expiry and driverId that are reused on every later finance call.

Which endpoints expose a courier's earnings?

GET /v1/payouts/history (payout history), GET /v1/payouts/{payoutId} (single payout) and GET /v1/earnings/summary (per-period earnings) all return amount, fee and status fields for the courier's deliveries.

Does the app expose bank-account or early-payment data?

Yes. The wallet endpoint returns the courier's balance together with a Brazilian bank account (bankCode, branchNumber, accountNumber, ownerDocument), and an early-payment plan endpoint exposes feeAmount, minAmount, maxAmount and request counters.

What data categories does the courier finance API cover?

Payouts, per-delivery earnings, balances, bank accounts, receivables anticipation and auth tokens — everything the courier sees on the earnings and payments screens.

Apps similar to iFood para Entregadores

  • Soy Rappi — Rappi's courier app is iFood's main gig rival in Brazil, paying couriers for deliveries that go beyond restaurants to pharmacies, supermarkets and convenience stores.
  • Loggi Entregador — Loggi is a Brazilian logistics platform whose courier app focuses on e-commerce parcels and documents rather than restaurant food, so riders often run it alongside food-delivery apps.
  • Lalamove Driver — Lalamove is a Hong Kong-founded delivery app operating in Brazil that dispatches jobs from motorcycles up to trucks and charges fixed fees instead of per-order commissions.
  • 99Food — 99Food is the food-delivery service Didi relaunched in Brazil in 2025 with a R$1 billion investment, recruiting couriers inside the 99 app ecosystem to challenge iFood.
  • Keeta — Keeta is the international delivery brand of Chinese giant Meituan, which entered Brazil in 2025 and began signing up couriers in São Paulo as a new iFood rival.
  • aiqfome — aiqfome is a Brazilian delivery platform owned by the Magalu group that concentrates on smaller interior cities, giving couriers outside the big capitals another source of orders.

Topics

  • ifood driver api
  • ifood entregador api
  • ifood payouts endpoint
  • ifood driver earnings api
  • ifood bank account api
  • ifood courier api
  • ifood early payment api

Need this app's data API integrated?

We deliver scoped integrations for any named app — from USD 500 with source-code handoff, or hosted access billed per call. Tell us the data you need.

  • NDA + SOW on every engagement
  • Delivery in 3–7 days
  • Payment only after acceptance
  • Work scoped to authorized use

Get a quote