Expense type fields - update

Recomputes the field definitions after a client-side change to one or more fields. Send the current fields payload as the request body — typically after a field marked requiresUpdate: true was edited — and the response returns the same shape with derived and dependent fields refreshed and any custom-field scripts re-evaluated. Unlike the GET variant, no fields are seeded from server-side records; the client's payload is the source of truth. Pass applyScanResult=<contentId> to fold receipt-scan results into the response.

Path Params
string
required
^[0-9a-fA-F]{32}$

The id of the organization of the user

string
enum
required

Expense type where CarSpecification relates to Mileage, SubsistenceAllowance to Per Diem, etc

Allowed:
Query Params
string
^[0-9a-fA-F]{32}$

scan result id that should be applied on the fields

Body Params

Fields format of expense record

fields
array of objects

Field-builder array describing the editable properties of the resource. Each entry pairs a property name with a value and any errors.

fields
validationErrors
array of objects

the list of errors occurred during the saving or sending the expense instance (record or report)

validationErrors
Response

Language
Credentials
Bearer
URL
LoadingLoading…
Response
Click Try It! to start a request and see the response here! Or choose an example:
application/json