Create Expense Entry
Creates a new Expense Entry
- application/json
Request Body
- vehicle_id integer required
Possible values:
>= 1
- expense_entry_type_id integer required
Possible values:
>= 1
- vendor_id integer
Possible values:
>= 1
- total_amount_cents integer required
The total amount of this Expense Entry, in cents.
- occurred_at date-time required
Date and time of the expense. We recommend using ISO-8601 formatted dates to avoid ambiguity.
- notes string
Additional comments.
- custom_fields object
*Full details on working with Custom Fields here.
- 201
- 401
- 422
- 500
OK
Response Headers
- application/json
- Schema
- Example (from schema)
Schema
- id integer
Possible values:
>= 1
- created_at date-time
The date and time at which this record was created.
- updated_at date-time
The date and time at which this record was most recently updated.
- total_amount float
The total amount of the expense.
- notes string
Additional comments.
- expense_entry_type_id integer
Possible values:
>= 1
- expense_entry_type_name string
Name of the Expense Entry Type associated with this entry.
- occurred_at date-time
Date and time of the expense.
- vehicle_id integer
The ID of the associated
Vehicle
. - vehicle_name string
The name of the associated
Vehicle
. - vendor_id NullableId
Possible values:
>= 1
- vendor_name string
The name of the associated
Vendor
. - custom_fields object
*Full details on working with Custom Fields here.
{
"id": 0,
"created_at": "2023-03-14T13:46:27-06:00",
"updated_at": "2023-03-14T13:46:27-06:00",
"total_amount": 0,
"notes": "string",
"expense_entry_type_id": 0,
"expense_entry_type_name": "string",
"occurred_at": "2023-03-14T13:46:27-06:00",
"vehicle_id": 0,
"vehicle_name": "string",
"vendor_id": 0,
"vendor_name": "string",
"custom_fields": {}
}
Request could not be authenticated
- application/json
- Schema
- Example (from schema)
Schema
- status integer
Possible values:
>= 400
and<= 599
- title string
A short, human-readable summary of the problem type. It SHOULD NOT change from occurrence to occurrence of the problem, except for purposes of localization.
- detail string
A human-readable explanation specific to this occurrence of the problem.
- instance string
A URI reference that identifies the specific occurrence of the problem. It may or may not yield further information if dereferenced.
{
"status": 0,
"title": "string",
"detail": "string",
"instance": "string"
}
Unprocessable Entity
- application/json
- Schema
- Example (from schema)
- Example
Schema
errors object
typeitems string
{
"errors": {}
}
{
"errors": {
"field1": [
"error1",
"error2"
],
"field2": [
"error3"
]
}
}
Something unexpected happened
- application/json
- Schema
- Example (from schema)
Schema
- status integer
Possible values:
>= 400
and<= 599
- title string
A short, human-readable summary of the problem type. It SHOULD NOT change from occurrence to occurrence of the problem, except for purposes of localization.
- detail string
A human-readable explanation specific to this occurrence of the problem.
- instance string
A URI reference that identifies the specific occurrence of the problem. It may or may not yield further information if dereferenced.
{
"status": 0,
"title": "string",
"detail": "string",
"instance": "string"
}