Expose both Posted Date (bookingDate) and Transaction Date (valueDate) in GET /transactions API

Currently, the GET /api/v1/accounts/{accountId}/transactions endpoint returns a single top-level date field. While the system processes multiple date fields from bank data (like valueDate and bookingDate) to determine this value 3, API consumers cannot access both dates separately, as far as I can tell 4

It would be useful if the returned both the raw transaction occurrence date (value date) and the posted date (booking date) as distinct fields in the response to allow API consumers to decide which date is most relevant for their specific integration and reconciliation use cases.