| GET | /v1.1/transactions/listpaymentactivity | ||
|---|---|---|---|
| GET | /v1.2/transactions/listpaymentactivity |
| Name | Parameter | Data Type | Required | Description |
|---|---|---|---|---|
| TransactionId | form | int | No | |
| TransactionType | form | string | No | |
| TransactionDate | form | DateTime | No | |
| Amount | form | decimal | No | |
| Notes | form | string | No | |
| FeeAmount | form | decimal | No | |
| Reason | form | string | No | |
| PayerName | form | string | No | |
| PayerAddress | form | string | No | |
| PayerEmail | form | string | No | |
| GroupName | form | string | No |
To override the Content-type in your clients, use the HTTP Accept Header, append the .xml suffix or ?format=xml
The following are sample HTTP requests and responses. The placeholders shown need to be replaced with actual values.
GET /v1.1/transactions/listpaymentactivity HTTP/1.1 Host: devapi.billhighway.com Accept: application/xml
HTTP/1.1 200 OK Content-Type: application/xml Content-Length: length <PaymentActivity xmlns:i="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://schemas.datacontract.org/2004/07/BH.CloudAPI.Common.Models"> <Amount>0</Amount> <FeeAmount>0</FeeAmount> <GroupName>String</GroupName> <Notes>String</Notes> <PayerAddress>String</PayerAddress> <PayerEmail>String</PayerEmail> <PayerName>String</PayerName> <Reason>String</Reason> <TransactionDate>0001-01-01T00:00:00</TransactionDate> <TransactionId>0</TransactionId> <TransactionType>String</TransactionType> </PaymentActivity>