Get Transactions

post

https://dispute-api-{corename}.{env}.gpsrv.com/getTransactions

👍
Availability
No new clients will be set up with Dispute API 2.0. Legacy clients will eventually be migrated to Dispute API 3.0.

Use the Get Transactions endpoint to retrieve the account holder transactions that are eligible to be disputed. You can filter the results by start date, end date, amount, and merchant name.

This endpoint is part of a conversational API—a series of endpoint calls that must be made in a certain order. For instructions see the Creating an API 2.0 Dispute guide.

Previous endpoint: Add Case Reasons
Next endpoint: Add Transactions

Form Data

apiLogin

string

required

Provider's web service username, as provided by Galileo for the requesting IP address.
Pattern: Max 50 characters
Example: "AbC123-9999"

apiTransKey

string

required

Web service password, as provided by Galileo for the requesting IP address.
Pattern: Max 15 characters
Example: "4sb62fh6w4h7w34g"

providerId

int32

required

Galileo-issued unique provider identifier.
Pattern: Max 10 digits
Example: 9999

transactionId

string

required

1 to 60

A provider-generated ID that is unique to each API call. A UUID is preferred. Do not reuse this identifier for multiple API calls.
Pattern: 60 characters or less
Example: "9845dk-39fdk3fj3-4483483478"

caseId

string

required

^$|^([0-9]{11}[A-Z]{1})$

Case identifier as returned by Create Case.
Pattern: Max 11 digits with a letter
Example: "22021000017C"

startDate

date

The starting date for the transactions to return.
Pattern: YYYY-MM-DD
Example: "2023-11-01"

endDate

date

The ending date of the transactions to return.
Pattern: YYYY-MM-DD
Example: "2023-11-30"

amount

float

0.01 to 999999999999.99

Amount of the transaction to return.
Pattern: Positive integer or decimal number
Example: 100.00, 100, or 100.73

merchantName

string

Name of the merchant that performed the transaction.
Pattern: string
Example: "DoorDash"

Response

default