Skip to main content

Create Expense Entry

Creates a new Expense Entry

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.

  • documents_attributes object[]

    An array of one or more document objects to add to the record. You may provide your own file_url, or follow our Attaching Documents and Images guide to upload to our third party storage provider.

  • 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 pointing 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. You may provide your own file_url, or follow our Attaching Documents and Images guide to upload to our third party storage provider.

  • 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 pointing 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

OK

Response Headers


    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.

    • account_id integer

      The ID of the Account that owns this Expense Entry.

    • notes string

      Additional comments.

    • expense_entry_type_id integer

      Possible values: >= 1

    • occurred_at date-time

      Date and time of the expense.

    • vehicle_id integer

      The ID of the associated Vehicle.

    • vendor_id NullableId

      Possible values: >= 1

    • custom_fields object

      *Full details on working with Custom Fields here.

    • billable_id integer

      The ID of the associated Acquisition, if applicable.

    • billable_type string

      Possible values: [Acquisition]

      The billable type, if applicable.

    • bulk_watch_record boolean

      Whether or not this record is being watched in bulk.

    • comments_count integer

      The number of Comments on this record.

    • documents_count integer

      The number of documents attached to this record.

    • images_count integer

      The number of images attached to this record.

    • import_id integer

      The ID of the Import that created this record, if applicable.

    • is_sample boolean

      Whether or not this record is sample data.

    • recurring_expense_entry_id integer

      The ID of the associated recurring Expense Entry, if applicable.

    • skip_automatic_watchers_callbacks boolean

      Whether or not to skip automatic watchers callbacks.

    • total_amount_cents string

      The total amount of the expense.

    • vehicle_archived_at date-time

      The date and time the associated Vehicle was archived, if applicable.

    • watchable_options object

      Options related to watching the record.

    Loading...