Adyen Disputeservice

Adyen Dispute Service is an API for retrieving and managing payment disputes, chargebacks, and related evidence workflows.

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.

adyendocumentfinancepayment

Adyen Disputeservice V30

Adyen Dispute Service is an API for retrieving and managing payment disputes, chargebacks, and related evidence workflows.

Base URL: https://ca-test.adyen.com/ca/services/DisputeService/v30
Auth: header:X-API-Key (pass your key via the apiKey input)

Operations

post_acceptdispute — POST /acceptDispute — Accept a dispute
post_defenddispute — POST /defendDispute — Defend a dispute
post_deletedisputedefensedocument — POST /deleteDisputeDefenseDocument — Delete a defense document
post_retrieveapplicabledefensereasons — POST /retrieveApplicableDefenseReasons — Get applicable defense reasons
post_supplydefensedocument — POST /supplyDefenseDocument — Supply a defense document

Inputs

apiKey — your adyen-disputeservice-v30 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: post_acceptdispute
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: post_acceptdispute, post_defenddispute, post_deletedisputedefensedocument, post_retrieveapplicabledefensereasons, post_supplydefensedocument
`body`	string	no	—	Request body as a JSON object string (for create/update operations).
`query`	string	no	—	Query-string parameters as a JSON object string, e.g. {"limit": 50}. Parsed and url-encoded onto the request.