Create Expense Entry

POST 
https://secure.fleetio.com/api/v1/expense_entries

Creates a new Expense Entry

Request

application/json

Body

vehicle_idId (integer)required
Possible values: >= 1
expense_entry_type_idId (integer)required
Possible values: >= 1
vendor_idId (integer)
Possible values: >= 1
total_amount_centsintegerrequired
The total amount of this Expense Entry, in cents.
occurred_atdate-timerequired
Date and time of the expense. We recommend using ISO-8601 formatted dates to avoid ambiguity.
Example: 2023-03-14T13:46:27-06:00
notesstring
Additional comments.
custom_fieldsobjectnullable
*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.
Array [
namestring
The name to give the file which will be shown in the UI.
Possible values: <= 255 characters
file_urlstring
The URL obtained from our storage provider that points to the file.
Possible values: <= 255 characters
file_mime_typestring
The MIME type of the file. For example, application/pdf.
Possible values: <= 255 characters
file_namestring
The name of the file.
Possible values: <= 255 characters
file_sizeinteger
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.
Array [
namestring
The name to give the image which will be shown in the UI.
Possible values: <= 255 characters
file_urlstring
The URL obtained from our storage provider that points to the image.
Possible values: <= 255 characters
file_mime_typestring
The MIME type of the image. For example, image/png.
Possible values: <= 255 characters
file_namestring
The name of the image.
Possible values: <= 255 characters
file_sizeinteger
The size of the image file in bytes.
]

Responses

201

OK

Response Headers

application/json

Schema

Schema

idId (integer)required

Possible values: >= 1

created_atdate-time

The date and time at which this record was created.

Example: 2023-03-14T13:46:27-06:00

updated_atdate-time

The date and time at which this record was most recently updated.

Example: 2023-03-14T13:46:27-06:00

account_idintegerrequired

The ID of the Account that owns this Expense Entry.

notesstringnullable

Additional comments.

expense_entry_type_idId (integer)required

Possible values: >= 1

occurred_atdate-timerequired

Date and time of the expense.

Example: 2023-03-14T13:46:27-06:00

vehicle_idintegerrequired

The ID of the associated Vehicle.

vendor_idNullableId (integer)nullablerequired

Possible values: >= 1

custom_fieldsobjectnullablerequired

*Full details on working with Custom Fields here.

billable_idintegernullable

The ID of the associated Acquisition, if applicable.

billable_typestringnullable

The billable type, if applicable.

Possible values: [Acquisition]

bulk_watch_recordboolean

Whether or not this record is being watched in bulk.

comments_countintegerrequired

The number of Comments on this record.

Possible values: >= 0

documents_countintegerrequired

The number of documents attached to this record.

Possible values: >= 0

images_countintegerrequired

The number of images attached to this record.

Possible values: >= 0

import_idintegernullable

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

is_sampleboolean

Whether or not this record is sample data.

recurring_expense_entry_idintegernullable

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

skip_automatic_watchers_callbacksboolean

Whether or not to skip automatic watchers callbacks.

total_amount_centsstringrequired

The total amount of the expense.

vehicle_archived_atdate-timenullable

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

watchable_optionsobjectrequired

Options related to watching the record.

Example (auto)

{
  "id": 0,
  "created_at": "2023-03-14T13:46:27-06:00",
  "updated_at": "2023-03-14T13:46:27-06:00",
  "account_id": 0,
  "notes": "string",
  "expense_entry_type_id": 0,
  "occurred_at": "2023-03-14T13:46:27-06:00",
  "vehicle_id": 0,
  "vendor_id": 0,
  "custom_fields": {},
  "billable_id": 0,
  "billable_type": "Acquisition",
  "bulk_watch_record": true,
  "comments_count": 0,
  "documents_count": 0,
  "images_count": 0,
  "import_id": 0,
  "is_sample": true,
  "recurring_expense_entry_id": 0,
  "skip_automatic_watchers_callbacks": true,
  "total_amount_cents": "string",
  "vehicle_archived_at": "2024-07-29T15:51:28.071Z",
  "watchable_options": {}
}

401

Request could not be authenticated

application/json

Schema

Schema

statusintegerrequired

Possible values: >= 400 and <= 599

titlestringrequired

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.

detailstring

A human-readable explanation specific to this occurrence of the problem.

instancestring

A URI reference that identifies the specific occurrence of the problem. It may or may not yield further information if dereferenced.

Example (auto)

{
  "status": 0,
  "title": "string",
  "detail": "string",
  "instance": "string"
}

422

Unprocessable Entity

application/json

Schema

Schema

errors object
property name* string[]
Array [
string
]

Example (auto)

{
  "errors": {}
}

Example

{
  "errors": {
    "field1": [
      "error1",
      "error2"
    ],
    "field2": [
      "error3"
    ]
  }
}

500

Something unexpected happened

application/json

Schema

Schema

statusintegerrequired

Possible values: >= 400 and <= 599

titlestringrequired

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.

detailstring

A human-readable explanation specific to this occurrence of the problem.

instancestring

A URI reference that identifies the specific occurrence of the problem. It may or may not yield further information if dereferenced.

Example (auto)

{
  "status": 0,
  "title": "string",
  "detail": "string",
  "instance": "string"
}

Authorization: Authorization

name: Authorizationtype: apiKeyin: headerdescription: Prefix the value with "Token", for example: "Token 76cbe06c49a64".
You can generate a new API key [here](https://secure.fleetio.com/api_keys).

name: Account-Tokentype: apiKeyin: headerdescription: You can find your Account-Token [here](https://secure.fleetio.com/api_keys)

• curl
• ruby
• python
• csharp
• go
• java
• nodejs
• php

• CURL

curl -L 'https://secure.fleetio.com/api/v1/expense_entries' \
-H 'Content-Type: application/json' \
-H 'Accept: application/json' \
-H 'Authorization: Token <Authorization>' \
-H 'Account-Token: <Authorization>' \
-d '{
  "vehicle_id": 0,
  "expense_entry_type_id": 0,
  "vendor_id": 0,
  "total_amount_cents": 0,
  "occurred_at": "2023-03-14T13:46:27-06:00",
  "notes": "string",
  "custom_fields": {},
  "documents_attributes": [
    {
      "name": "string",
      "file_url": "string",
      "file_mime_type": "string",
      "file_name": "string",
      "file_size": 0
    }
  ],
  "images_attributes": [
    {
      "name": "string",
      "file_url": "string",
      "file_mime_type": "string",
      "file_name": "string",
      "file_size": 0
    }
  ]
}'

Request Collapse all

Base URL

https://secure.fleetio.com/api

Auth

apiKey

accountToken

Body

{
  "vehicle_id": 0,
  "expense_entry_type_id": 0,
  "vendor_id": 0,
  "total_amount_cents": 0,
  "occurred_at": "2023-03-14T13:46:27-06:00",
  "notes": "string",
  "custom_fields": {},
  "documents_attributes": [
    {
      "name": "string",
      "file_url": "string",
      "file_mime_type": "string",
      "file_name": "string",
      "file_size": 0
    }
  ],
  "images_attributes": [
    {
      "name": "string",
      "file_url": "string",
      "file_mime_type": "string",
      "file_name": "string",
      "file_size": 0
    }
  ]
}

ResponseClear

Click the Send API Request button above and see the response here!