Review what is owed before you export a PayPal file.

API and MCP access needs the Plus plan. The PayPal mass-payment file is an admin export. It is not one of the 31 API operations.

A merchant might ask, "Who is unpaid, and what would a payout file contain?" The agent can read the ledger and the paid flags. The person who pays still marks commissions paid in AffiliateLauncher and exports the PayPal file there. The app's own description of payment is: commissions accrue in the ledger, you mark them paid, and you can export a PayPal mass-payment file.

What the API returns

GET /api/v1/ledger/entries in the OpenAPI file searches ledger entries. A row has a transaction date, a transaction type, an amount, a description, a status, a payout type when one applies, paymentIsLocked, and simpleCommIsPaid. POST /api/v1/ledger/entries creates a manual adjustment. It requires an affiliate id and an amount. That post does not send money and it does not create the PayPal file.

Sales carry the same paid flag: simpleCommIsPaid and simpleCommCommissionAmount on GET /api/v1/sales. MCP adds get_distributor_earnings and get_commission_overview for the same kind of question.

What stays in the admin

• Marking a commission paid.
• Exporting the PayPal mass-payment file.
• The 1099-ready payee totals export. Filing stays with you or your accountant. That export is not in the public API operation list.

Commission runs can be finalized, which the API describes as posting earnings to the ledger, and rolled back when the period allows. Those routes belong to the tier that includes them. The other tier uses real-time plans.