/bff/expense/update
Update expense (payer + supplier swaps allowed on any status)
ExpensepostBffExpenseUpdate
Parameters
15 body
Body · 15
externalIdstringRequiredLength: 24–24
descriptionstringLength: 1–∞
categorystring | string | string | string | string | string | string | string | string | string | string | string | string | string | stringaccountCodestring | nullvatRatenumber | nulltotalMoneynumber | nullnetMoneynumber | nullvatMoneynumber | nulleffectiveDatestringdueDatestring | nullpaidDatestring | nullpaymentMethodstring | nullinternalNotestring | nullpayerContactExternalIdstring | nullExternal id of the new "PLÁTCE" contact. null clears the link; omit to keep the current value. Editing the payer is allowed even on terminal rows because it does not move money — it just re-attributes who owes what.
supplierContactExternalIdstring | nullExternal id of the new "PŘÍJEMCE" contact. Same tri-state as payer: null clears, omit keeps. Editing the supplier is allowed on terminal rows for the same reason.
Request
POST /bff/expense/update
curl -X POST "https://api.bizkithub.com/bff/expense/update" \
-H "Content-Type: application/json" \
-H "Authorization: Bearer YOUR_API_KEY" \
-d '{
"externalId": "example_externalId",
"description": "example_description",
"effectiveDate": "example_effectiveDate"
}'Response
JSON payload
{
"success": true,
"changeCount": 0
}All response codes
1 status code documented
Need an API key?
All BizKitHub API endpoints require authentication via API key.