batch_export_payments
Code
batch_export_payments › Request Body
The export selection. Exactly the string "all" (Process All Eligible, scoped by the sibling filters) OR a non-empty list of commission-payment id (UUID) strings. Any other value (a non-"all" scalar, an object, an empty list, or a non-UUID element) is rejected with success=false before any money moves.
api_keyAPI key for the caller (consumed by the gateway for authentication). Optional here; the endpoint authorizes the session operator via permissions.
is_electronic_paymentGrid filter; only applied when commission_payment_ids == "all". Ignored for an explicit id list.
commission_month^\d{4}-(0[1-9]|1[0-2…YYYY-MM report month (month 01-12); only applied when commission_payment_ids == "all". Ignored for an explicit id list.
Grid status filter; only applied when commission_payment_ids == "all". Ignored for an explicit id list.
searchGrid search filter; only applied when commission_payment_ids == "all". Ignored for an explicit id list.
batch_export_payments › Responses
successWhether the export request was accepted. False on request validation (bad commission_payment_ids, missing explicit id) or ambiguous routing (more than one active ACH_ISSUANCE instance).
The export result.
create_adjustment
Code
create_adjustment › Request Body
adjustment_amountThe adjustment amount (USD, 2 decimal places). Required on both the source-ful and source-less paths. Negative values are chargebacks (money taken back from the agency). Accepted as a JSON number or as a decimal string; a string form is coerced server-side.
source_accounting_idThe ID of the source commission_accounting row to copy the policy, agency and agent from. OMIT this field to use the source-less path (policy-free agency chargeback), which instead requires agency_id, agent_id, adjustment_amount, period_start and period_end.
adjustment_reasonFree-text cause for the adjustment. Stored in commission_accounting.why. On the SOURCE-LESS path it is REQUIRED: it must be present, non-blank, and 150 characters or fewer. Non-blankness is evaluated AFTER server-side sanitization, so a markup-only value such as '' (which sanitizes to an empty string) is rejected; the 150-character limit is measured on the submitted value, and a longer value is rejected with a validation error rather than truncated. On the SOURCE-FUL path it remains optional, and an omitted value defaults to the literal 'User generated manual adjustment'. The 150-character limit is source-less-only, which is why it is described here in prose instead of as a JSON-Schema maxLength keyword. For MVR chargebacks the orchestrator supplies a human-readable cause built from the quote number, named insured and MVR pull date.
reason_codeCategorization code for the adjustment. Validated dynamically against the COMMISSION_ADJUSTMENT_REASONS quick code rather than a fixed enum, so the accepted values are whatever that quick code contains for the site. Seeded values are CORRECTION (the system default), BONUS and CHARGEBACK. When omitted on the source-less path the quick-code default (CORRECTION) is applied.
agency_idThe ID of the agency the adjustment is booked against (the payee). Required on the source-less path. Must be a contact holding the Agency role. The check verifies role membership only -- it does not verify the contact is active. Ignored on the source-ful path, where the agency is copied from the source commission_accounting row.
agent_idThe ID of the crediting agent for the adjustment. Required on the source-less path. Must be a contact holding the Agent role. The check verifies role membership only -- it does not verify the contact is active. Ignored on the source-ful path, where the agent is copied from the source commission_accounting row.
period_startStart of the commission period the adjustment covers. Required on the source-less path. Format: YYYY-mm-ddTHH:MM:SSZ (e.g. 2020-01-01T12:00:00Z). This is UTC time.
period_endEnd of the commission period the adjustment covers. Required on the source-less path. This value is snapped to the end of its month (last day, 23:59:59) and the snapped value is stored as the row's transaction date, so it determines which monthly commission payment period the chargeback rolls up into. The month is chosen AFTER the value is converted to America/Chicago, so a UTC instant just past midnight on the 1st (e.g. 2026-08-01T00:00:00Z) lands in the PREVIOUS month (July 31, not August 31). Policy-free rows are not yet rendered on the monthly commission statement document (BC-23074): the chargeback changes the agency's commission payment amount but does not appear as a statement detail line. Format: YYYY-mm-ddTHH:MM:SSZ (e.g. 2020-01-01T12:00:00Z). This is UTC time.
create_adjustment › Responses
The result of the commission adjustment operation
successWhether the operation was successful
get_delayed_commission_accounting_entries
Code
get_delayed_commission_accounting_entries › Request Body
get_delayed_commission_accounting_entries › Responses
List of delayed commission accounting entries
total_entriesTotal count of delayed entries
total_commissionable_amountSum of all commissionable amounts as decimal string
total_amount_to_be_paidSum of all amounts to be paid as decimal string
Contact identifiers for inserted_by fields
get_payment
Gets a commission payment record.
Code
get_payment › Request Body
payment_idThe unique identifier of the payment (claim transaction id)
get_payment › Responses
The payment object ClaimExposurePaymentModel
successget_regenerate_statements_status
Code
get_regenerate_statements_status › Request Body
yearFour-digit calendar year of the report month (e.g. 2026). Must be supplied together with month.
monthCalendar month of the report month, 1-12. Must be supplied together with year.
get_regenerate_statements_status › Responses
The current state of the async job.
successWhether the poll request itself was accepted (the job's own status is in data.async_status / data.success).
regenerate_statements
Code
regenerate_statements › Request Body
yearFour-digit calendar year of the report month (e.g. 2026). Must be supplied together with month.
monthCalendar month of the report month, 1-12. Must be supplied together with year.
regenerate_statements › Responses
The async job handle. The caller polls get_regenerate_statements_status with reference_id until async_status reaches a terminal state.
successWhether the request to start the job was accepted.
write_off_agency_commissions
Code
write_off_agency_commissions › Request Body
agency_idThe ID of the agency to write off all negative entries for
write_off_reasonThe reason for writing off the commissions. 'collected_from_agency' indicates the balance was collected from the agency. 'forgiven' indicates the balance was written off/forgiven.
whyUser-provided description/reason for the write-off. This is stored in the commission_accounting.why field.
write_off_agency_commissions › Responses
The result of the agency write-off operation
successWhether the operation was successful
