Version
READ

list_partner_payouts

List the cash payouts Subscriby made to the token's creator as a partner — the amount, the rail, the transfer's reference and how many commissions each covered. Read-only.

Page the cash Subscriby paid the partner, newest first, in the shape GET /v1/me/partner/payouts answers. Payouts are recorded by Subscriby when the money has left, so there is nothing to filter and nothing to write. Commissions settled as Subscriby Credit are not payouts; they read as credited on list_partner_rewards.

Read-only. Never mutates anything.

Requires ability

The token behind the MCP session must hold it, or the call is refused with TOKEN_MISSING_ABILITY.

Runs the same action as

The REST endpoint and this tool share one action, so validation, permissions and events are identical.

Annotations

Read-only

It reads and never changes anything.

Arguments

limitintegeroptional

Maximum payouts to return per page (1..100).

min1max100
pageintegeroptional

1-indexed page number.

min1

What it returns

{  "data": [    {      "id": "0b1c2d3e-4f50-4617-8a9b-0c1d2e3f4a5b",      "amount": "117.0000",      "currency": "USD",      "method": "paypal",      "reference": "PAYPAL-7F3D1C92",      "note": null,      "paid_at": "2026-11-01T06:30:00+00:00",      "rewards_paid": 10,      "created_at": "2026-11-01T06:30:00+00:00"    }  ],  "meta": { "page": 1, "limit": 25, "total": 1, "has_more": false }}

method is the rail the money went by: paypal, wise, remitly or crypto (USDT on TRC20). rewards_paid is how many approved commissions the payout covered, oldest first.

How it fails

RESOURCE_NOT_FOUND

the creator never applied to the programme.

AUTHENTICATION_REQUIRED

no authenticated user on the request.

TOKEN_MISSING_ABILITY

token lacks account:read.

How is this guide?

Last updated on