Create a new temporary-expense-item.
Attaching a receipt: if the expense nature requires a receipt, you must first upload the file via POST /lucca-files/api/uploads, then create an ExpenseReceipt via POST /api/v3/expenseReceipts, and finally reference the receipt’s id in the expenseReceipts array. Do not pass the file upload ID directly — see the Attaching receipts guide for the full workflow.
API key. Value must be formatted like so: lucca application={api_key}.
The ExpenseTempItem, or "temporary expense" is an expense that has not yet been declared (within an expense report) by its owner (the user who made the expense). Once submitted within an expense report, the expense turns into an ExpenseClaimItem.
Day the expense was made.
Expense amount in original currency.
Various amounts in the establishment's currency.
Nature of the expense: Meals, Train, Taxi, Hotels, Taxi, Mileage... List depends on the app configuration.
x >= 1The quantity when the expense type is 'Quantity'.
x >= 1Unique identifier of the user that made this expense.
How this expense was made: the owner used his money, an enterprise debit card, or a Cleemy card:
0, 1, 3 "Web"Additional information when the expense type is mileage.
Additional information when the expense type is 'Invitation'.
Values for custom fields.
Merchant of the expense.
The expense receipts (PDF file, image, ...) attached to this expense. Technically, there could be more than one, but in reality, there’s usually just one.
Important: to attach a receipt when creating or updating an expense, you must first upload the file via POST /lucca-files/api/uploads, then create an ExpenseReceipt via POST /api/v3/expenseReceipts (providing the uploadId), and finally reference the receipt by its id here. Passing the file upload ID directly will result in a 403 Forbidden error. See the Attaching receipts guide.
The source describes how the expense was created:
Status of the expense.
OK
The ExpenseTempItem, or "temporary expense" is an expense that has not yet been declared (within an expense report) by its owner (the user who made the expense). Once submitted within an expense report, the expense turns into an ExpenseClaimItem.