identity_id
identity.idFilter by the source instrument id. Must be specified when source.type is provided.
identity.idqueryFilter by the source instrument id. Must be specified when source.type is provided.
pattern ^[0-9]+$
identity.typequeryFilter by the source instrument type. Must be specified when source.id is provided.
Indicates the identity type.
Enum:CONSUMERCORPORATE
offsetqueryThe offset value for paging, indicating the initial item number to be returned from the data set satisfying the given criteria. Leave out to fetch the first page of results.
min 0
limitqueryThe limit of the results for paging, starting at the offset. Limit is always capped at 100.
min 1max 100
createdFromqueryFilter for managed accounts/cards created after createdFrom timestamp. Timestamp is expressed in Epoch timestamp using millisecond precision. Leave out to fetch all managed accounts/cards.
createdToqueryFilter for managed accounts/cards created before createdTo timestamp. Timestamp is expressed in Epoch timestamp using millisecond precision. Leave out to fetch all managed accounts/cards.
orderByTimestampqueryOrders the result in ascending or descending order.
If not specified, the transactions will be returned in descending order.
Enum:ASCDESC
statusqueryEnum:SUBMITTEDRUNNINGPARTIALLY_COMPLETEDCOMPLETEDFAILEDPAUSEDCANCELLED
bulk_idpath*The bulk id of the bulk process.
pattern ^[0-9]+$
sequencequerystatusqueryEnum:SUBMITTEDRUNNINGCOMPLETEDFAILEDCANCELLED
idempotency-refheaderA unique call reference generated by the caller that, taking into consideration the payload as well as the operation itself, helps avoid duplicate operations. Idempotency reference uniqueness is maintained for at least 24 hours.
acceptheaderA request parameter specifying the type of response the client would like. Must be one of application/json, application/pdf or text/csv.
The default response type (application/json) will be returned if specified incorrectly or not specified.
statementLimitqueryThe limit of the results for statements paging, starting at the offset. Limit is capped at 500.
min 1max 500
fromTimestampqueryFilter for transactions having transaction timestamp after fromTimestamp. Timestamp is expressed in Epoch timestamp using millisecond precision. If omitted, all matching transactions up to the present will be included.
toTimestampqueryFilter for transactions having transaction timestamp before toTimestamp. Timestamp is expressed in Epoch timestamp using millisecond precision. If omitted, all matching transactions up to the present will be included. If both fromTimestamp and toTimestamp are provided, toTimestamp must be greater than fromTimestamp.
showFundMovementsOnlyqueryDeprecated. Use singleEntryPerTransaction instead.
Returns only the entries which contain fund movements.
singleEntryPerTransactionqueryReturns transactions that span multiple movements as a single entry. Only includes transactions that have been completed. Defaults to true for PDF statements, false otherwise. Note: due to the fact that only completed transactions are included, some transactions that are in progress and have modified the balance of the instrument will not be shown, which could lead to seemingly inconsistent balance being displayed.
transactionTypequeryFilter by the transaction type. Leave out to fetch all entries.
Enum:INSTRUMENT_CREATEINSTRUMENT_BLOCKINSTRUMENT_UNBLOCKINSTRUMENT_DELETEAUTHORISATIONSETTLEMENTMANUAL_TRANSACTIONTRANSFERSENDDEPOSITAUTHORISATION_REVERSALAUTHORISATION_EXPIRYAUTHORISATION_DECLINEAUTHORISATION_MANUAL_CLOSEMERCHANT_REFUNDMERCHANT_REFUND_REVERSALORIGINAL_CREDIT_TRANSACTIONSETTLEMENT_REVERSALADJUSTMENTCHARGE_FEEWITHDRAWAL_RESERVEWITHDRAWAL_RELEASEFEE_REVERSALCARD_UPGRADE_TO_PHYSICALACTIVATE_PHYSICAL_CARDINSTRUMENT_REPLACEOUTGOING_WIRE_TRANSFERAUTHORISATION_CANCELLATIONSYSTEM_TRANSACTIONOUTGOING_DIRECT_DEBIT_COLLECTIONOUTGOING_DIRECT_DEBIT_REFUND
unique items true
profileIdqueryFilter by the transfer profile. Leave out to fetch all transfer transactions.
The profile Id which a specific identity, instrument or transaction type is linked to.
Profiles contain configuration and determine behavioral aspects of the newly created transaction, for example, fees that may apply.
You can have one or more profiles linked to your application, and these can be used to drive different behaviors according to your product's needs.
Profile Ids can be found in the Multi Portal, in the API Credentials page.
pattern ^[0-9]+$
instrumentIdqueryFilter by the source instrument id.
statequeryFilter by the transfer transaction state. Leave out to fetch all states.
Enum:INITIALISEDCOMPLETEDREJECTEDFAILEDPENDINGSCHEDULEDCANCELLED
unique items true
createdFromqueryFilter for transfer transactions created after createdFrom timestamp. Timestamp is expressed in Epoch timestamp using millisecond precision. Leave out to fetch all transfers.
createdToqueryFilter for transfer transactions created before createdTo timestamp. Timestamp is expressed in Epoch timestamp using millisecond precision. Leave out to fetch all transfers.
tagqueryFilter by the transfer tag. The exact tag must be provided, as wildcards are not supported. Leave out to fetch all entries.
user_idpath*The unique identifier for the user.
pattern ^[0-9]+$