5002: Has transaction
Returns a boolean value indicating whether a transaction has been logged for the user with a specific group and type - optionally filtered by time period.
Endpoint ID: | 5002 | |||||||||
Method: | GET | |||||||||
URL: | /entity/id/{entity-id}/transactions/{transaction-group-id}/has/{transaction-type-id}?from={from-date}&to={to-date} /entity/ext-key/{ext-key}/{ext-type}/transactions/{transaction-group-id}/has/{transaction-type-id}?from={from-date}&to={to-date} | |||||||||
| entity-id | Rubiq entity ID that uniquely identifies the account to check transactions for | ||||||||
| ext-key | External key that uniquely identifies the account to check transactions for | ||||||||
| ext-type | Type of external key | ||||||||
| transaction-group-id | Numeric value identifying the transaction group to search for. This ID is documented in the contract between dialogportal™ and the application | ||||||||
| transaction-type-id | Numeric value identifying the transaction type to search for. This ID is documented in the contract between dialogportal™ and the application | ||||||||
| from-date | Optional date value limiting the search to only include transactions after this date. The date must be in UTC and formatted as "yyyymmddZ", for example "20140321Z" (21 March 2014). | ||||||||
| to-date | Optional date value limiting the search to only include transactions before this date. The date must be in UTC and formatted as "yyyymmddZ", for example "20140321Z" (21 March 2014). | ||||||||
Request body: | None | |||||||||
Response body: | Boolean value indicating whether a transaction exists
| |||||||||
Status codes: | 200 | Transaction existence checked with success | ||||||||
| 404 | Account, transaction group or transaction type was not found The following sub codes may be returned:
| ||||||||