List your transaction fees
/v1/me/transaction-fees in the Transaction Fees API.
curl "https://api.subscriby.net/v1/me/transaction-fees?month=2026-10&channel=metered" \ -H "Authorization: Bearer $SUBSCRIBY_TOKEN"Pages the ledger, the most recently incurred first. month keeps one calendar month (YYYY-MM, UTC) and wins over from and to, which bound the window by instant; project_id keeps one project's lines; channel is connect_at_source or metered; kind is payment_fee, access_code_fee, trial_usage, outage_emails or processing_recovery. Sort with sort_by (occurred_at by default, or fee_amount, units, kind, channel, created_at) and sort_direction.
Each row names what the fee was for and, for a payment's fee, the project, the member, the purchase and the payment it was priced from with the gross amount, the currency and the rate applied. fee_amount is in fee_currency, your billing currency; units are the cents the meter counted, zero on a fee taken at source. A line of a different kind (a trial's waived fees, a recovery's emails, an invoice's processing recovery) carries its meter_identifier and no payment.
Requires ability
The token must hold this ability, or the call is refused with 403.
MCP tool
Runs the same action from an agent, behind the same ability.
Authorization
bearerToken A personal access token minted on the dashboard under Settings, then Tokens, sent as Authorization: Bearer sbt_live_…. The token carries the abilities each endpoint lists under Requires ability and is frozen to one team.
In: header
Query Parameters
Keep only the lines of one calendar month, as YYYY-MM in UTC, such as 2026-10; wins over from and to.
Keep only lines incurred at or after this instant, ISO 8601.
date-timeKeep only lines incurred before this instant, ISO 8601.
date-timeKeep only the lines earned on this project.
uuidKeep only lines collected one way: connect_at_source (deducted from the member's payment by Stripe Connect) or metered (billed on your own Subscriby invoice).
Value in
- "connect_at_source"
- "metered"
Keep only lines of one kind: payment_fee, access_code_fee, trial_usage, outage_emails or processing_recovery.
Value in
- "payment_fee"
- "access_code_fee"
- "trial_usage"
- "outage_emails"
- "processing_recovery"
The 1-based page to return. A page past the last answers an empty data array with meta.total still filled, so a loop can stop without guessing.
1 <= value1Rows per page, 1 to 100. A higher value clamps to the cap silently. Defaults to 25.
1 <= value <= 10025The column to order by. Defaults to created_at; a column the endpoint does not offer falls back to the default rather than failing.
"created_at"asc or desc. Defaults to desc.
"desc"Value in
- "asc"
- "desc"
Legacy alias of per_page, kept for clients that predate it. per_page wins when both are sent.
1 <= value <= 100Responses
200OKapplication/json
The page.
401UnauthorizedAUTHENTICATION_REQUIREDapplication/json
The request carries no bearer token, or one that is revoked, malformed, or minted for another environment (an sbt_test_ token on production).
403ForbiddenTOKEN_MISSING_ABILITYapplication/json
The token is valid but does not carry the ability this endpoint requires; error.context.required_ability names the one to grant. An endpoint that also checks who owns a row or which tier the account is on answers FORBIDDEN, TEAM_TIER_REQUIRED or CONNECTOR_TIER_REQUIRED with the same status, and says so in its own description.
422Validation failedVALIDATION_FAILEDapplication/json
The payload broke a rule, and error.fields maps each offending key to its messages. A refusal from the domain, such as a plan that cannot go on sale or a member who cannot be removed, uses the same code with error.message saying why and no fields.
On this endpoint: VALIDATION_FAILED: when month is not YYYY-MM, a bound is not a date, project_id is not an id, or channel or kind is not one of the words above.
429Too many requestsRATE_LIMITEDapplication/json
The token has spent its 300 requests a minute or 10,000 an hour; Retry-After says when the next one is accepted.
How is this guide?
Last updated on
Transaction Fees API
Transaction Fees are what Subscriby charges a creator on the money their members pay: a percentage of each payment at the plan's rate, a code redeemed past the plan's free allotment, the metered fees a platform trial waived, emails sent to members during a recovery, and the cost of collecting an invoice's fee lines.
Get a month's fee summary
/v1/me/transaction-fees/summary in the Transaction Fees API.