iFood para Entregadores——骑手财务数据 API
iFood 骑手端的收入、结算与钱包界面,背后是一套私有 HTTPS 数据 API。应用通过 POST /v1/identity/session 完成骑手登录,再以 Bearer 令牌调用 GET /v1/payouts/history、GET /v1/earnings/summary 与 GET /v1/wallet 等端点,拉取收入汇总、提现记录与当前余额。
下方端点覆盖骑手财务链路的核心:从会话认证、按周期结算的提现明细,到巴西本地银行账户与应收款提前兑付计划。
iFood para Entregadores 是巴西最大外卖网络的骑手配套应用。在其收入界面背后,是一套骑手财务数据 API,完整覆盖骑手的收入、结算与银行账户信息。
应用截图
API 端点一览
OAuth2 骑手令牌签发
POST
/v1/identity/sessionopenfinance认证骑手身份(密码 / 验证码 / 生物识别 / 刷新令牌等授权方式),返回后续调用所需的 Bearer 令牌。
认证方式: 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-..." }依据应用界面推导;端点细节为示意说明,并非实际抓包。
reconstructed from the app's courier sign-in and session flowmatches the token payload consumed by every earnings screen
查询历史提现记录
GET
/v1/payouts/historyopenfinance按周期返回骑手的汇总提现历史(汇总 + 明细列表),含付款方式与状态。
认证方式: 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} ] }依据应用界面推导;端点细节为示意说明,并非实际抓包。
reconstructed from the app's payout history ('Meus Repasses') flowconsistent with the period/paymentType filters on the payouts screen
查询提现详情
GET
/v1/payouts/{payoutId}openfinance读取单笔提现的完整明细(金额、手续费、结算周期、状态),用于提现详情页。
认证方式: 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 }依据应用界面推导;端点细节为示意说明,并非实际抓包。
reconstructed from the app's payout detail screen
查询计费收入汇总
GET
/v1/earnings/summaryopenfinance把骑手每笔配送的计费条目按日期区间聚合成收入总额。
认证方式: 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} ] }依据应用界面推导;端点细节为示意说明,并非实际抓包。
reconstructed from the app's weekly earnings flowmatches the date-range totals shown on the earnings screen
查询余额与支付方式
GET
/v1/walletopenfinance同时读取骑手当前余额 / 支付列表,以及已绑定的巴西本地银行账户。
认证方式: 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"} }依据应用界面推导;端点细节为示意说明,并非实际抓包。
reconstructed from the app's balance and bank-account flow
查询应收款提前兑付计划
GET
/v1/advance-pay/planopenfinance返回骑手的提前收款(应收款兑付)计划:费率、单笔最小 / 最大金额与可兑付额度。
认证方式: 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} }依据应用界面推导;端点细节为示意说明,并非实际抓包。
reconstructed from the app's early-payment offer flowconsistent with the fee and limit copy on the anticipation screen
数据类别
- 提现
- 收入
- 余额
- 支付
- 银行账户
- 应收款提前兑付
- 认证令牌
数据使用场景与案例
零工骑手薪资对账
记账工具每晚拉取合并的打款历史与单笔打款明细,把打款日期、金额、手续费与银行流水逐笔核对,让骑手的账目自动轧平。
车队收入看板
车队运营方聚合旗下骑手的每周收入汇总——周金额、账单条目与每日明细——用于排名产能、预测每周现金支出。
应收款提前变现
信贷产品读取提前回款计划(手续费、最低/最高金额、回款频率)并结合钱包余额,为骑手预审应收款提前变现额度。
常见问题
iFood 骑手端使用什么数据 API?
应用调用一套私有 HTTPS API:登录走 POST /v1/identity/session(OAuth2 密码 / 验证码 / 生物识别 / 刷新令牌),登录后通过 GET /v1/payouts/history、GET /v1/earnings/summary 等端点以 JSON 返回收入与结算数据。
该 API 如何认证?
骑手先通过 POST /v1/identity/session 获取 Bearer 访问令牌(支持密码、短信验证码、生物识别与刷新令牌多种授权方式),之后所有财务端点都凭该令牌访问;没有公开的开发者密钥。
能否程序化读取骑手收入?
应用自身的收入界面由 GET /v1/earnings/summary 驱动,按日期区间聚合每笔配送的计费条目;提现历史则由 GET /v1/payouts/history 返回。两者都是需要会话令牌的私有端点,而非公开 API。
应收款提前兑付端点是什么?
GET /v1/advance-pay/plan 返回骑手的提前收款计划:手续费率、单笔最小 / 最大金额与可提前兑付的应收余额,对应应用内的提前收款界面。
相关主题
- iFood 骑手 API
- ifood entregador api
- iFood 提现端点
- 骑手收入 API
- iFood 银行账户接口
- 应收款提前兑付