Return every money transfer that occurred on a specific local calendar day within the authenticated user’s active wallet. The server converts the supplied date to the client’s timezone, computes the UTC-equivalent midnight-to-midnight window, and queries the database with those UTC bounds. Results are ordered by transfer ID descending (newest first) and include the same full transfer shape as the other list endpoints. This endpoint is designed for the daily view in the Life Cost UI, where a user taps a day in the calendar and sees all transactions for that day in their local time.Documentation Index
Fetch the complete documentation index at: https://mintlify.com/akevalion/life_cost/llms.txt
Use this file to discover all available pages before exploring further.
Endpoint
Authentication
Required. The request must be made with an active session cookie obtained through the Google OAuth login flow.Request Body
An IANA timezone identifier string (e.g.
"America/New_York", "Europe/Madrid", "Asia/Tokyo"). Used to localise the supplied date and to define the day boundaries before converting to UTC for the database query.An ISO 8601 date-time string representing any moment within the target day (e.g.
"2024-01-15T00:00:00Z" or "2024-01-15T12:00:00+05:30"). The server extracts the calendar date in the given timeZone and queries from 00:00:00 to 23:59:59.999999 of that day.Response
An array of transfer objects in the same shape returned byGET /last_money_transfers/<limit>. An empty array is returned if there are no transfers on the specified day.
The unique identifier of the transfer.
Human-readable description of the transfer.
Transfer amount. Negative for expenses, positive for income.
ISO 8601 timestamp (UTC) when the transfer was created.
ISO 8601 timestamp (UTC) of the last modification. Field name is
modifed_at (single i) matching the database column.Category/tag objects for this transfer.
username of the user who created the transfer.Example Request
Example Request Body
Example Response
Error Cases
| Status | Condition |
|---|---|
302 Found | The user is not authenticated. |
400 Bad Request | The request body is missing date or timeZone, or date cannot be parsed as ISO 8601. |
500 Internal Server Error | timeZone is not a valid IANA timezone identifier and pytz raises an exception. |