Billing Runs: Creates and runs a billing run for the caller's reseller scope.
POST
/api/billing-runs
deprecated
Requires: MerchantBilling.BillingRuns, MerchantBilling.BillingRuns.Create, merchant scope.
A reseller caller (or an admin acting inside a reseller's context) runs that single reseller; an admin with no reseller context fans out across every reseller with billable merchants. Set `ResellerId` to run one named reseller instead: the caller's own or one beneath it (an admin may name any). Set `IsDryRun` on the input for a preview that calculates charges without generating invoices.
Example request
Every block below sends the same request. Replace {{BASE_URL}} with the address of the API you are calling and {{API_KEY}} with your own key.
The request body is a CreateBillingRunInput. See the Request body section below for its fields.
Parameters
| Name | In | Type | Description |
|---|---|---|---|
suppressNulls
required |
query | boolean | If true, omit properties with null values. |
Request body
application/json
, required
| Field | Type | Description |
|---|---|---|
periodKey
required |
string | Billing period key in yyyyMM format (e.g., "202602" for February 2026). nullablemin length 0max length 10 |
isDryRun
required |
boolean | When true, calculates charges without generating invoices (preview mode). |
resellerId
required |
string (uuid) | Optional reseller to run billing for. Omit it to run for the caller's own reseller (or, for an admin with no reseller selected, to bill every reseller). When set, the run bills that one reseller's merchants; a reseller caller may name their own reseller or any reseller beneath it, and an admin may name any reseller. A reseller outside the caller's scope is reported as not found. Not accepted by the all-resellers trigger. Conditional: When ResellerId is not null. nullable |
This request body has no documented fields.
Responses
200 The run was created (or the fan-out was started).
Body: BillingRunBatchResultDto
Each item has these fields.
| Field | Type | Description |
|---|---|---|
periodKey
required |
string | Billing period key (yyyyMM) the batch was run for. nullable |
isDryRun
required |
boolean | True when charges were previewed without generating invoices/charges. |
wasFanOut
required |
boolean | True when this was an admin cross-reseller fan-out; false for a single-reseller run. Drives whether the UI shows the multi-reseller summary or the single-run message. |
isAsyncStarted
required |
boolean | True when the fan-out was started as a Durable background process rather than run inline: the per-reseller counts in this result are not yet populated. Callers track progress via `BillingRunBatchStatusDto` (`batchId`). |
batchId
required |
string (uuid) | The background batch id when `isAsyncStarted` is true; otherwise null. nullable |
resellersConsidered
required |
integer (int32) | Number of resellers evaluated (the full set considered for the run). |
resellersRun
required |
integer (int32) | Number of resellers for which a billing run actually executed. |
resellersSkipped
required |
integer (int32) | Number of resellers skipped without running: no billable merchants for the period, or a completed run already exists / is in progress for the period. |
resellersFailed
required |
integer (int32) | Number of resellers whose run failed. |
totalMerchantsBilled
required |
integer (int32) | Total merchants successfully billed across every reseller run in the batch. |
totalMerchantsFailed
required |
integer (int32) | Total merchants that failed within the executed reseller runs. A run can complete at the reseller level while individual merchants fail; this surfaces those so the toast severity reflects them (a fan-out with merchant failures is not a clean success). |
outcomes
required |
array of BillingRunResellerOutcomeDto | Per-reseller outcomes. nullable |
This response has no documented body fields.
403 Forbidden
Body: RemoteServiceErrorResponse
Each item has these fields.
| Field | Type | Description |
|---|---|---|
error
required |
RemoteServiceErrorInfo |
This response has no documented body fields.
401 Unauthorized
Body: RemoteServiceErrorResponse
Each item has these fields.
| Field | Type | Description |
|---|---|---|
error
required |
RemoteServiceErrorInfo |
This response has no documented body fields.
400 Bad Request
Body: RemoteServiceErrorResponse
Each item has these fields.
| Field | Type | Description |
|---|---|---|
error
required |
RemoteServiceErrorInfo |
This response has no documented body fields.
404 The named reseller does not exist or is outside the caller's reseller scope.
Body: RemoteServiceErrorResponse
Each item has these fields.
| Field | Type | Description |
|---|---|---|
error
required |
RemoteServiceErrorInfo |
This response has no documented body fields.
501 Not Implemented
Body: RemoteServiceErrorResponse
Each item has these fields.
| Field | Type | Description |
|---|---|---|
error
required |
RemoteServiceErrorInfo |
This response has no documented body fields.
500 Internal Server Error
Body: RemoteServiceErrorResponse
Each item has these fields.
| Field | Type | Description |
|---|---|---|
error
required |
RemoteServiceErrorInfo |
This response has no documented body fields.
default The request failed. The body carries the standard error envelope: a machine-readable `error.code`, a human-readable `error.message`, and `error.validationErrors` when the failure was a validation rejection. See the error-code reference in this document's description for the values `error.code` can take.
Body: RemoteServiceErrorResponse
Each item has these fields.
| Field | Type | Description |
|---|---|---|
error
required |
RemoteServiceErrorInfo |
This response has no documented body fields.
429 The request was refused because a rate limit was exceeded. Wait at least the interval `Retry-After` names before retrying, then back off. Limits are tuned per deployment, so read the allowance from the response headers rather than assuming a fixed ceiling.
Body: RateLimitProblemDetails
Each item has these fields.
| Field | Type | Description |
|---|---|---|
type
required |
string | The problem type identifier. Always the same value: the failure is the status code itself, so there is no sub-type for a caller to branch on. nullable |
title
required |
string | A short, human-readable summary of the problem type. nullable |
status
required |
integer (int32) | The HTTP status code, repeated in the body as the problem-details format defines. |
detail
required |
string | A human-readable explanation of this occurrence of the problem. nullable |
retryAfterSeconds
required |
integer (int32) | How long to wait before retrying, in whole seconds, carrying the same figure as the `Retry-After` header. Always at least one: a value of zero would invite an immediate retry that is certain to be rejected again. |
This response has no documented body fields.
Errors
A failed request returns the platform error envelope. The
error reference lists every value
error.code can carry and shows the four response shapes.