API reference · Getting paid

Collection splits

GET Read how one receipt was actually split

GET /collection/receipt/{reference}/splits

The amounts here are the ones that will settle, computed once when the money arrived and never recomputed - a split recalculated at settlement time could answer differently after a rate change. The rounding residue is carried on the row it was assigned to, so a recipient who is a minor unit up or down can be shown exactly why.

Headers

NameNotes
AuthorizationBearer token
X-TenantYour tenant
X-Environmenttest or live

Path parameters

Name
reference

Example

Response: GenericResponseListReceiptSplitResponse

curl -X GET "https://api.bridgemoni.com/collection/receipt/b3f1c2d4-5e6a-4b7c-8d9e-0f1a2b3c4d5e/splits" \
  -H "Authorization: Bearer $BRIDGEMONI_TOKEN" \
  -H "X-Tenant: $BRIDGEMONI_TENANT" \
  -H "X-Environment: $BRIDGEMONI_ENV"

Responses

StatusWhen
200Receipt splits retrieved successfully

GET Read how a collection will be split

GET /collection/request/{reference}/splits

Splits are declared when the request is created and frozen from that moment: they were disclosed to the recipients and a payer pays against them, so changing who gets what afterwards would be re-directing somebody else's money. Percentages are taken against the net, after the marketplace's own charges, which is why they can sum to a hundred without leaving the platform short.

Headers

NameNotes
AuthorizationBearer token
X-TenantYour tenant
X-Environmenttest or live

Path parameters

Name
reference

Example

Response: GenericResponseListRequestSplitResponse

curl -X GET "https://api.bridgemoni.com/collection/request/b3f1c2d4-5e6a-4b7c-8d9e-0f1a2b3c4d5e/splits" \
  -H "Authorization: Bearer $BRIDGEMONI_TOKEN" \
  -H "X-Tenant: $BRIDGEMONI_TENANT" \
  -H "X-Environment: $BRIDGEMONI_ENV"

Responses

StatusWhen
200Splits retrieved successfully

Generated from the OpenAPI document. Branch on the HTTP status: there is no machine-readable error code on the wire. Errors