OpenAPI Update (#901)

Update OpenAPI for cd033404b6f260b270bafe1d98f8db4110bfb918 Co-authored-by: Stripe OpenAPI <105521251+stripe-openapi[bot]@users.noreply.github.com>
stripe · Jul 5, 2024 · 6ccc58f · 6ccc58f
1 parent 9e59657
commit 6ccc58f
Show file tree

Hide file tree

Showing 3 changed files with 24 additions and 1 deletion.
diff --git a/embedded/openapi/fixtures3.json b/embedded/openapi/fixtures3.json
@@ -4173,7 +4173,8 @@
         "tax_code": "txcd_92010001"
       },
       "tax_date": 1234567890,
-      "type": "transaction"
+      "type": "transaction",
+      "posted_at": 2008020787
     },
     "tax.transaction_line_item": {
       "amount": 1499,

diff --git a/embedded/openapi/spec3.beta.sdk.json b/embedded/openapi/spec3.beta.sdk.json
@@ -63448,6 +63448,11 @@
             ],
             "type": "string"
           },
+          "posted_at": {
+            "description": "The Unix timestamp representing when the tax liability is assumed or reduced.",
+            "format": "unix-time",
+            "type": "integer"
+          },
           "reference": {
             "description": "A custom unique identifier, such as 'myOrder_123'.",
             "maxLength": 5000,
@@ -63503,6 +63508,7 @@
           "livemode",
           "metadata",
           "object",
+          "posted_at",
           "reference",
           "reversal",
           "ship_from_details",
@@ -190381,6 +190387,11 @@
                     "description": "Set of [key-value pairs](https://stripe.com/docs/api/metadata) that you can attach to an object. This can be useful for storing additional information about the object in a structured format. Individual keys can be unset by posting an empty value to them. All keys can be unset by posting an empty value to `metadata`.",
                     "type": "object"
                   },
+                  "posted_at": {
+                    "description": "The Unix timestamp representing when the tax liability is assumed or reduced, which determines the liability posting period and handling in tax liability reports. The timestamp must fall within the `tax_date` and the current time, unless the `tax_date` is scheduled in advance. Defaults to the current time.",
+                    "format": "unix-time",
+                    "type": "integer"
+                  },
                   "reference": {
                     "description": "A custom order or sale identifier, such as 'myOrder_123'. Must be unique across all transactions, including reversals.",
                     "maxLength": 500,

diff --git a/embedded/openapi/spec3.json b/embedded/openapi/spec3.json
@@ -44157,6 +44157,11 @@
             ],
             "type": "string"
           },
+          "posted_at": {
+            "description": "The Unix timestamp representing when the tax liability is assumed or reduced.",
+            "format": "unix-time",
+            "type": "integer"
+          },
           "reference": {
             "description": "A custom unique identifier, such as 'myOrder_123'.",
             "maxLength": 5000,
@@ -44210,6 +44215,7 @@
           "id",
           "livemode",
           "object",
+          "posted_at",
           "reference",
           "tax_date",
           "type"
@@ -145028,6 +145034,11 @@
                     "description": "Set of [key-value pairs](https://stripe.com/docs/api/metadata) that you can attach to an object. This can be useful for storing additional information about the object in a structured format. Individual keys can be unset by posting an empty value to them. All keys can be unset by posting an empty value to `metadata`.",
                     "type": "object"
                   },
+                  "posted_at": {
+                    "description": "The Unix timestamp representing when the tax liability is assumed or reduced, which determines the liability posting period and handling in tax liability reports. The timestamp must fall within the `tax_date` and the current time, unless the `tax_date` is scheduled in advance. Defaults to the current time.",
+                    "format": "unix-time",
+                    "type": "integer"
+                  },
                   "reference": {
                     "description": "A custom order or sale identifier, such as 'myOrder_123'. Must be unique across all transactions, including reversals.",
                     "maxLength": 500,