| POST | /Accounts/Transactions | ||
|---|---|---|---|
| POST | /AccountTransactions |
| Name | Parameter | Data Type | Required | Description |
|---|---|---|---|---|
| PropertyManagerID | body | string | No | The property manager ID (or customer code ID) that can manage the account(s) requested |
| AccountNumbers | body | List<long> | No | The list of account numbers for which to receive transaction data |
| FromDate | body | DateTime | Yes | The earliest date (in short DateTime format) for which to find transactions in the specified date range |
| ToDate | body | DateTime | Yes | The most recent date (in short DateTime format) for which to find transactions in the specified date range |
| Name | Parameter | Data Type | Required | Description |
|---|---|---|---|---|
| IsSuccessful | form | bool | No | Identifies whether the request executed successfully, however does not indicated requested data was found |
| StatusCode | form | int | No | The status code returned by the service |
| StatusMessage | form | string | No | The status message returned by the service |
| ServiceDebugFields | form | Dictionary<string, string> | No |
To override the Content-type in your clients, use the HTTP Accept Header, append the .json suffix or ?format=json
To embed the response in a jsonp callback, append ?callback=myCallback
The following are sample HTTP requests and responses. The placeholders shown need to be replaced with actual values.
POST /Accounts/Transactions HTTP/1.1
Host: services.allianceassociationbank.com
Accept: application/json
Content-Type: application/json
Content-Length: length
{"PropertyManagerID":"String","AccountNumbers":[0],"FromDate":"String","ToDate":"String"}
HTTP/1.1 200 OK
Content-Type: application/json
Content-Length: length
{"IsSuccessful":false,"StatusCode":0,"StatusMessage":"String","ServiceDebugFields":{"ApiServiceHost":"WAB-WEBPW02","ApiServiceHostVersion":"1.0.0.0"}}