diff --git a/json/ManagementService-v1.json b/json/ManagementService-v1.json index da8dd2b..733849e 100644 --- a/json/ManagementService-v1.json +++ b/json/ManagementService-v1.json @@ -18656,7 +18656,7 @@ ] }, "scheduledAt" : { - "description" : "The date and time when the action should happen. \nFormat: [RFC 3339](https://www.rfc-editor.org/rfc/rfc3339), but without the **Z** before the time offset. For example, **2021-11-15T12:16:21+01:00** \nThe action is sent with the first [maintenance call](https://docs.adyen.com/point-of-sale/automating-terminal-management/terminal-actions-api#when-actions-take-effect) after the specified date and time in the time zone of the terminal. \nAn empty value causes the action to be sent as soon as possible: at the next maintenance call.", + "description" : "The date and time when the action should happen. \nFormat: [RFC 3339](https://www.rfc-editor.org/rfc/rfc3339), but without the **Z** before the time offset. For example, **2021-11-15T12:16:21+0100** \nThe action is sent with the first [maintenance call](https://docs.adyen.com/point-of-sale/automating-terminal-management/terminal-actions-api#when-actions-take-effect) after the specified date and time in the time zone of the terminal. \nAn empty value causes the action to be sent as soon as possible: at the next maintenance call.", "type" : "string" }, "storeId" : { @@ -18705,7 +18705,7 @@ "type" : "array" }, "scheduledAt" : { - "description" : "The date and time when the action should happen. \nFormat: [RFC 3339](https://www.rfc-editor.org/rfc/rfc3339), but without the **Z** before the time offset. For example, **2021-11-15T12:16:21+01:00** \nThe action is sent with the first [maintenance call](https://docs.adyen.com/point-of-sale/automating-terminal-management/terminal-actions-api#when-actions-take-effect) after the specified date and time in the time zone of the terminal. \nAn empty value causes the action to be sent as soon as possible: at the next maintenance call.", + "description" : "The date and time when the action should happen. \nFormat: [RFC 3339](https://www.rfc-editor.org/rfc/rfc3339), but without the **Z** before the time offset. For example, **2021-11-15T12:16:21+0100** \nThe action is sent with the first [maintenance call](https://docs.adyen.com/point-of-sale/automating-terminal-management/terminal-actions-api#when-actions-take-effect) after the specified date and time in the time zone of the terminal. \nAn empty value causes the action to be sent as soon as possible: at the next maintenance call.", "type" : "string" }, "storeId" : { @@ -19585,7 +19585,7 @@ "additionalProperties" : false, "properties" : { "billingEntityId" : { - "description" : "The identification of the billing entity to use for the order.", + "description" : "The identification of the billing entity to use for the order. \n\n > When ordering products in Brazil, you do not need to include the `billingEntityId` in the request.", "type" : "string" }, "customerOrderReference" : { diff --git a/json/ManagementService-v3.json b/json/ManagementService-v3.json index c64f2e5..acdf57b 100644 --- a/json/ManagementService-v3.json +++ b/json/ManagementService-v3.json @@ -18946,7 +18946,7 @@ ] }, "scheduledAt" : { - "description" : "The date and time when the action should happen. \nFormat: [RFC 3339](https://www.rfc-editor.org/rfc/rfc3339), but without the **Z** before the time offset. For example, **2021-11-15T12:16:21+01:00** \nThe action is sent with the first [maintenance call](https://docs.adyen.com/point-of-sale/automating-terminal-management/terminal-actions-api#when-actions-take-effect) after the specified date and time in the time zone of the terminal. \nAn empty value causes the action to be sent as soon as possible: at the next maintenance call.", + "description" : "The date and time when the action should happen. \nFormat: [RFC 3339](https://www.rfc-editor.org/rfc/rfc3339), but without the **Z** before the time offset. For example, **2021-11-15T12:16:21+0100** \nThe action is sent with the first [maintenance call](https://docs.adyen.com/point-of-sale/automating-terminal-management/terminal-actions-api#when-actions-take-effect) after the specified date and time in the time zone of the terminal. \nAn empty value causes the action to be sent as soon as possible: at the next maintenance call.", "type" : "string" }, "storeId" : { @@ -18995,7 +18995,7 @@ "type" : "array" }, "scheduledAt" : { - "description" : "The date and time when the action should happen. \nFormat: [RFC 3339](https://www.rfc-editor.org/rfc/rfc3339), but without the **Z** before the time offset. For example, **2021-11-15T12:16:21+01:00** \nThe action is sent with the first [maintenance call](https://docs.adyen.com/point-of-sale/automating-terminal-management/terminal-actions-api#when-actions-take-effect) after the specified date and time in the time zone of the terminal. \nAn empty value causes the action to be sent as soon as possible: at the next maintenance call.", + "description" : "The date and time when the action should happen. \nFormat: [RFC 3339](https://www.rfc-editor.org/rfc/rfc3339), but without the **Z** before the time offset. For example, **2021-11-15T12:16:21+0100** \nThe action is sent with the first [maintenance call](https://docs.adyen.com/point-of-sale/automating-terminal-management/terminal-actions-api#when-actions-take-effect) after the specified date and time in the time zone of the terminal. \nAn empty value causes the action to be sent as soon as possible: at the next maintenance call.", "type" : "string" }, "storeId" : { @@ -19928,7 +19928,7 @@ "additionalProperties" : false, "properties" : { "billingEntityId" : { - "description" : "The identification of the billing entity to use for the order.", + "description" : "The identification of the billing entity to use for the order. \n\n > When ordering products in Brazil, you do not need to include the `billingEntityId` in the request.", "type" : "string" }, "customerOrderReference" : { diff --git a/yaml/ManagementService-v1.yaml b/yaml/ManagementService-v1.yaml index b3c2915..fccf291 100644 --- a/yaml/ManagementService-v1.yaml +++ b/yaml/ManagementService-v1.yaml @@ -13109,7 +13109,7 @@ components: scheduledAt: description: "The date and time when the action should happen. \nFormat:\ \ [RFC 3339](https://www.rfc-editor.org/rfc/rfc3339), but without the\ - \ **Z** before the time offset. For example, **2021-11-15T12:16:21+01:00**\ + \ **Z** before the time offset. For example, **2021-11-15T12:16:21+0100**\ \ \nThe action is sent with the first [maintenance call](https://docs.adyen.com/point-of-sale/automating-terminal-management/terminal-actions-api#when-actions-take-effect)\ \ after the specified date and time in the time zone of the terminal.\ \ \nAn empty value causes the action to be sent as soon as possible: at\ @@ -13149,7 +13149,7 @@ components: scheduledAt: description: "The date and time when the action should happen. \nFormat:\ \ [RFC 3339](https://www.rfc-editor.org/rfc/rfc3339), but without the\ - \ **Z** before the time offset. For example, **2021-11-15T12:16:21+01:00**\ + \ **Z** before the time offset. For example, **2021-11-15T12:16:21+0100**\ \ \nThe action is sent with the first [maintenance call](https://docs.adyen.com/point-of-sale/automating-terminal-management/terminal-actions-api#when-actions-take-effect)\ \ after the specified date and time in the time zone of the terminal.\ \ \nAn empty value causes the action to be sent as soon as possible: at\ @@ -14016,7 +14016,9 @@ components: additionalProperties: false properties: billingEntityId: - description: The identification of the billing entity to use for the order. + description: "The identification of the billing entity to use for the order.\ + \ \n\n > When ordering products in Brazil, you do not need to include\ + \ the `billingEntityId` in the request." type: string customerOrderReference: description: The merchant-defined purchase order reference. diff --git a/yaml/ManagementService-v3.yaml b/yaml/ManagementService-v3.yaml index 35e31c9..72e30cb 100644 --- a/yaml/ManagementService-v3.yaml +++ b/yaml/ManagementService-v3.yaml @@ -13296,7 +13296,7 @@ components: scheduledAt: description: "The date and time when the action should happen. \nFormat:\ \ [RFC 3339](https://www.rfc-editor.org/rfc/rfc3339), but without the\ - \ **Z** before the time offset. For example, **2021-11-15T12:16:21+01:00**\ + \ **Z** before the time offset. For example, **2021-11-15T12:16:21+0100**\ \ \nThe action is sent with the first [maintenance call](https://docs.adyen.com/point-of-sale/automating-terminal-management/terminal-actions-api#when-actions-take-effect)\ \ after the specified date and time in the time zone of the terminal.\ \ \nAn empty value causes the action to be sent as soon as possible: at\ @@ -13336,7 +13336,7 @@ components: scheduledAt: description: "The date and time when the action should happen. \nFormat:\ \ [RFC 3339](https://www.rfc-editor.org/rfc/rfc3339), but without the\ - \ **Z** before the time offset. For example, **2021-11-15T12:16:21+01:00**\ + \ **Z** before the time offset. For example, **2021-11-15T12:16:21+0100**\ \ \nThe action is sent with the first [maintenance call](https://docs.adyen.com/point-of-sale/automating-terminal-management/terminal-actions-api#when-actions-take-effect)\ \ after the specified date and time in the time zone of the terminal.\ \ \nAn empty value causes the action to be sent as soon as possible: at\ @@ -14289,7 +14289,9 @@ components: additionalProperties: false properties: billingEntityId: - description: The identification of the billing entity to use for the order. + description: "The identification of the billing entity to use for the order.\ + \ \n\n > When ordering products in Brazil, you do not need to include\ + \ the `billingEntityId` in the request." type: string customerOrderReference: description: The merchant-defined purchase order reference.