Adyen Clouddeviceservice

Adyen Cloud Device Service is an API for managing cloud-connected payment terminal devices used with Adyen in-person payments.

Type: Tool
Category: Finance
Version: 1.0.0
Provider: InTouch AI
License: MIT

Provided free and as is, without warranty of any kind — including merchantability, fitness for a particular purpose, and the accuracy or completeness of any result. See the licence. You are responsible for checking what this produces before relying on it.

adyenfinancepaymentstatus

Adyen Clouddeviceservice V1

Adyen Cloud Device Service is an API for managing cloud-connected payment terminal devices used with Adyen in-person payments.

Base URL: https://device-api-test.adyen.com/v1
Auth: header:X-API-Key (pass your key via the apiKey input)

Operations

get_merchants_merchantaccount_connecteddevices — GET /merchants/{merchantAccount}/connectedDevices — Get a list of connected devices
get_merchants_merchantaccount_devices_deviceid_s — GET /merchants/{merchantAccount}/devices/{deviceId}/status — Get the connection status of a device
post_merchants_merchantaccount_devices_deviceid_ — POST /merchants/{merchantAccount}/devices/{deviceId}/async — Send a Terminal API request and receive an asynchronous response

Inputs

apiKey — your adyen-clouddeviceservice-v1 API key
operation — one of the operations above
path parameters when an operation's path contains {...}
query — optional JSON object of query params
body — JSON object for create/update ops

Example

operation: get_merchants_merchantaccount_connecteddevices
apiKey: <your key>

Publishes

The keys a later task may reference as {{taskName.key}}. Referencing anything not listed here resolves to nothing at run time.

error
operation
result
status

Input Properties

Every property this tool accepts, from its own tool.iml.

Property	Type	Required	Default	Description
`apiKey`	string	yes	—	DEPRECATED — bind an API Key credential to the task with `credentialName` instead. A key pasted here is stored in the workflow definition in clear and appears in every export of it. Still honoured for workflows built before the change.
`operation`	string	yes	—	One of: get_merchants_merchantaccount_connecteddevices, get_merchants_merchantaccount_devices_deviceid_s, post_merchants_merchantaccount_devices_deviceid_
`deviceId`	string	no	—	Path parameter deviceId (required by some operations).
`merchantAccount`	string	no	—	Path parameter merchantAccount (required by some operations).
`query`	string	no	—	Optional query params as a JSON object string, e.g. {"limit": 10}.
`body`	string	no	—	Request body as a JSON object string (for create/update operations).