Update Expense Entry

Update a Expense Entry

Path Parameters

• id string required

  Possible values: Value must match regular expression ^[0-9]+$

  The id of the relevant record

application/json

Request Body

• vehicle_id integer

  Possible values: >= 1

• expense_entry_type_id integer

  Possible values: >= 1

• vendor_id integer

  Possible values: >= 1

• total_amount_cents integer

  The total amount of this Expense Entry, in cents.

• occurred_at date-time

  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.

• documents_attributes object[]

  An array of one or more document objects to add to the record. Follow our Attaching Documents and Images guide to upload to our third party storage provider in order to obtain file_url.

  name string

  Possible values: <= 255 characters

  The name to give the file which will be shown in the UI.

  file_url string

  Possible values: <= 255 characters

  The URL obtained from our storage provider that points to the file.

  file_mime_type string

  Possible values: <= 255 characters

  The MIME type of the file. For example, application/pdf.

  file_name string

  Possible values: <= 255 characters

  The name of the file.

  file_size integer

  The size of the file in bytes.

• images_attributes object[]

  An array of one or more image objects to add to the record. Follow our Attaching Documents and Images guide to upload to our third party storage provider in order to obtain file_url.

  name string

  Possible values: <= 255 characters

  The name to give the image which will be shown in the UI.

  file_url string

  Possible values: <= 255 characters

  The URL obtained from our storage provider that points to the image.

  file_mime_type string

  Possible values: <= 255 characters

  The MIME type of the image. For example, image/png.

  file_name string

  Possible values: <= 255 characters

  The name of the image.

  file_size integer

  The size of the image file in bytes.

Responses

• 204
• 401
• 403
• 404
• 422
• 500

---

OK

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"
}

Insufficient permission to perform this operation

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"
}

The requested resource could not be located

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

  type

  items 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"
}

Loading...