@lunch-money/v2-api-spec 2.9.1 → 2.9.2

package/lunch-money-api-v2.yaml

@@ -42,7 +42,7 @@ info:
   license:
     name: Apache 2.0
     url: http://www.apache.org/licenses/LICENSE-2.0.html
-  version: 2.9.1
+  version: 2.9.2
 
 servers:
   - url: https://api.lunchmoney.dev/v2
@@ -1531,14 +1531,10 @@ components:
             Name of payee set by the user, the financial institution, or by 
             a matched recurring item. This will match the value 
             displayed in payee field on the transactions page in the GUI.
-          minLength: 0
-          maxLength: 140
         original_name:
           type: string
           nullable: true
           description: Original payee name from the source (financial institution, CSV, etc.). For Plaid transactions, this is the raw name before normalization. For manual/API transactions, this typically matches `payee`. May be null for older transactions.
-          minLength: 0
-          maxLength: 140
         category_id:
           type: integer
           format: int32
@@ -1805,14 +1801,10 @@ components:
             Name of payee set by the user, the financial institution, or by 
             a matched recurring item. This will match the value 
             displayed in payee field on the transactions page in the GUI.
-          minLength: 0
-          maxLength: 140
         original_name:
           type: string
           nullable: true
           description: Original payee name from the source (financial institution, CSV, etc.). For Plaid transactions, this is the raw name before normalization. For manual/API transactions, this typically matches `payee`. May be null for older transactions.
-          minLength: 0
-          maxLength: 140
         category_id:
           type: integer
           format: int32
@@ -2050,14 +2042,10 @@ components:
         payee:
           type: string
           description: Name of payee for the transaction
-          minLength: 0
-          maxLength: 140
         original_name:
           type: string
           nullable: true
           description: Original payee name. If not provided, defaults to `payee` value.
-          minLength: 0
-          maxLength: 140
         category_id:
           type: integer
           format: int32
@@ -2190,15 +2178,11 @@ components:
           type: string
           description: |
             The new payee for the transaction.
-          minLength: 0
-          maxLength: 140
           x-updatable: true
         original_name:
           type: string
           nullable: true
           description: Original payee name. Cannot be changed. Ignored if set.
-          minLength: 0
-          maxLength: 140
           x-updatable: false
         category_id:
           type: integer

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@lunch-money/v2-api-spec",
-  "version": "2.9.1",
+  "version": "2.9.2",
   "description": "OpenAPI specification and version history for the Lunch Money v2 API",
   "main": "lunch-money-api-v2.yaml",
   "files": [

package/version-history.md

@@ -5,6 +5,9 @@ The Lunch Money API spec uses a modified version of SEMVER for its versioning me
 - The minor version represents the number of main endpoints the current version of the spec supports.  For example, a version of the API that supports the /me, /categories, and /transactions endpoints would have a minor version of 3.
 - The revision number represents the number of updates since the last endpoint was added.  For example, each time changes are made to one of the existing three APIs as described above, the revision number will be bumped.
 
+## v2.9.2 - Apr 22, 2026
+- Increase allowable length for a transaction `payee`
+
 ## v2.9.1 - Apr 22, 2026
 - You may now set `archived_at` when modifying a category or tag via the `PUT /categories` or `PUT /tags` endpoints.
 
@@ -349,4 +352,3 @@ This is the initial branch using the versioning described above
 - It is the v2 version of the API - hence the major version 2.
 - The API Spec currently supports 3 endpoints /me, /categories, and /transactions.  hence the minor version 3.
 - This version of the spec contains minor modifications to the previously published spec and therefore has a revision number 1
-