Changelog
This changelog contains the newly added endpoints and also the updates that are made to the already available endpoints, in chronological order. This documentation will provide a high overview of what have been added and/or updated. Visit our API documentation for a more descriptive information on the deployed / to be deployed changes.
Each colour represents different deployment phases:
- Upcoming deployment in all environments
- Current deployment in UAT environment and will be deployed in production environment in the stipulated date.
- Current deployment in production environment (if no further change logs are specified, this is also the current deployment in UAT environment)
- Past deployment in all environments
The version number of the developer's documentation, will be updated when a deployment is in UAT or already in production!
19 Aug 2024 TBA
Deployment Date | Environment |
---|---|
10 Sep 2024 | UAT |
10 Sep 2024 | Production |
Modified endpoints:
- POST /accounts/{account_id}/credit - Credit the account id
- Property
transaction_code
will be mandatory
- Property
- POST /accounts/{account_id}/debit - Debit the account id
- Property
transaction_code
will be mandatory
- Property
- GET /accounts/{account_id}/transactions - Retrieve all transactions by account id
- Enum values
AccountLoad
,CashLoad
,CreditCardLoad
,DebitCardLoad
,VoucherLoad
,SepaIncomingPayment
andSepaOutgoingPayment
in propertyprocessing_code_type
will now be returned according to the transaction codes used in the credit and debit endpoints.
- Enum values
- GET /cards/{card_id}/transactions - Retrieve all transactions by card id
- Enum values
AccountLoad
,CashLoad
,CreditCardLoad
,DebitCardLoad
,VoucherLoad
,SepaIncomingPayment
andSepaOutgoingPayment
in propertyprocessing_code_type
will now be returned according to the transaction codes used in the credit and debit endpoints.
- Enum values
- GET /accounts/{account_id}/transactions/{transaction_id} - Retrieve transaction details by account id and transaction id
- Enum values
AccountLoad
,CashLoad
,CreditCardLoad
,DebitCardLoad
,VoucherLoad
,SepaIncomingPayment
andSepaOutgoingPayment
in propertyprocessing_code_type
will now be returned according to the transaction codes used in the credit and debit endpoints.
- Enum values
- GET /corporate/accounts/{corporate_account_id}/transactions - Retrieve all transactions by corproate account id
- Enum values
AccountLoad
,CashLoad
,CreditCardLoad
,DebitCardLoad
,VoucherLoad
,SepaIncomingPayment
,SepaOutgoingPayment
,SepaIncomingPaymentAdjustment
andSepaOutgoingPaymentAdjustment
in propertyprocessing_code_type
will now be returned according to the transaction codes used in the credit and debit endpoints.
- Enum values
- GET /corporate/accounts/{account_id}/transactions/{transaction_id} - Retrieve transaction details by corproate account id and transaction id
- Enum values
AccountLoad
,CashLoad
,CreditCardLoad
,DebitCardLoad
,VoucherLoad
,SepaIncomingPayment
,SepaOutgoingPayment
,SepaIncomingPaymentAdjustment
andSepaOutgoingPaymentAdjustment
in propertyprocessing_code_type
will now be returned according to the transaction codes used in the credit and debit endpoints.
- Enum values
29 Aug 2024 1.27
Deployment Date | Environment |
---|---|
29 Aug 2024 | UAT |
29 Aug 2024 | Production |
Modified endpoints:
- GET /accounts/{account_id}/transactions - Retrieve all transactions by account id
- Paging sizing to change from 500 to 50
- Adding enum values
AccountLoad
,CashLoad
,CreditCardLoad
,DebitCardLoad
,VoucherLoad
,SepaIncomingPayment
andSepaOutgoingPayment
in propertyprocessing_code_type
which will be returned according to the transaction codes used in the credit and debit endpoints (currently these have only been added in the documentation, they will be returned in the endpoint responses in a future release).
- GET /cards/{card_id}/transactions - Retrieve all transactions by card id
- Paging sizing to change from 500 to 50
- Adding enum values
AccountLoad
,CashLoad
,CreditCardLoad
,DebitCardLoad
,VoucherLoad
,SepaIncomingPayment
andSepaOutgoingPayment
in propertyprocessing_code_type
which will be returned according to the transaction codes used in the credit and debit endpoints (currently these have only been added in the documentation, they will be returned in the endpoint responses in a future release).
- GET /accounts/{account_id}/transactions/{transaction_id} - Retrieve transaction details by account id and transaction id
- Adding enum values
AccountLoad
,CashLoad
,CreditCardLoad
,DebitCardLoad
,VoucherLoad
,SepaIncomingPayment
andSepaOutgoingPayment
in propertyprocessing_code_type
which will be returned according to the transaction codes used in the credit and debit endpoints (currently these have only been added in the documentation, they will be returned in the endpoint responses in a future release).
- Adding enum values
- GET /corporate/accounts/{corporate_account_id}/transactions - Retrieve all transactions by corproate account id
- Paging sizing to change from 500 to 50
- Adding enum values
AccountLoad
,CashLoad
,CreditCardLoad
,DebitCardLoad
,VoucherLoad
,SepaIncomingPayment
,SepaOutgoingPayment
,SepaIncomingPaymentAdjustment
andSepaOutgoingPaymentAdjustment
in propertyprocessing_code_type
which will be returned according to the transaction codes used in the credit and debit endpoints (currently these have only been added in the documentation, they will be returned in the endpoint responses in a future release).
- GET /corporate/accounts/{account_id}/transactions/{transaction_id} - Retrieve transaction details by corproate account id and transaction id
- Adding enum values
AccountLoad
,CashLoad
,CreditCardLoad
,DebitCardLoad
,VoucherLoad
,SepaIncomingPayment
,SepaOutgoingPayment
,SepaIncomingPaymentAdjustment
andSepaOutgoingPaymentAdjustment
in propertyprocessing_code_type
which will be returned according to the transaction codes used in the credit and debit endpoints (currently these have only been added in the documentation, they will be returned in the endpoint responses in a future release).
- Adding enum values