jlengrand/adyen-openapi
1
0
Fork 0
mirror of https://github.com/gcatanese/adyen-openapi.git synced 2026-03-10 08:01:24 +00:00
Code Issues Packages Projects Releases Wiki Activity

spec release

Browse Source
This commit is contained in:
Adyen Automation
2024-04-05 09:05:05 +02:00
parent 4ab8c7858f
commit c0c6bf1156
4 changed files with 16 additions and 12 deletions
Download Patch File Download Diff File Expand all files Collapse all files

6
json/ManagementService-v1.json
View File

@@ -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" : {

6
json/ManagementService-v3.json
View File

@@ -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" : {

8
yaml/ManagementService-v1.yaml
View File

@@ -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.

8
yaml/ManagementService-v3.yaml
View File

@@ -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.