List of breaking changes introduced to the VRP APIs
2025.1, 2024.2_SP5, 2024.2_SP4, 2024.2_SP3
API | Major Version to which the Breaking Change was introduced |
---|---|
Central Transaction Repository API | v3 |
Changed data types for parameters:
- We changed the data type from long to string in the response for
operatorUserRoleNumber
,loyaltyInfo.approverId
, andauthorizedBy.approverUserRoleNumber
fields in theGET /documents/unified
endpoint. - We changed the data type from long to string in the response for
operatorUserRoleNumber
,loyaltyInfo.approverId
, andauthorizedBy.approverUserRoleNumber
fields in theGET /documents/unified/{ctrTransactionId}
endpoint. - We changed the data type from long to string in the response for
operatorUserRoleNumber
,loyaltyInfo.approverId
, andauthorizedBy.approverUserRoleNumber
fields in thePOST /documents/unified-list
endpoint.
Impacted endpoints:
- GET /documents/unified
- GET /documents/unified/{ctrTransactionId}
- POST /documents/unified-list
2025.1, 2024.2_SP4, 2024.2_SP3
API | Major Version to which the Breaking Change was introduced |
---|---|
Master Data API | v3 |
Changed data types for parameters:
- We changed the data type from numbers to array of long in the request
id
field. It was changed from int32 to int64 in theGET /timeRestrictions
endpoint. - We changed the data type from numbers to long in the response
id
field. It was changed from int32 to int64 in theGET /timeRestrictions
endpoint.
Impacted endpoints:
- GET /timeRestrictions
2025.1, 2024.2_SP4
API | Major Version to which the Breaking Change was introduced |
---|---|
Master Data API | v3 |
Changed data types for parameters:
- We changed the data type from integer to string in the request
id
field in thePOST users/bulk-load
endpoint. - We changed the data type from array[integer] to array[string] in the request
id
field and the responseid
field (from integer to string) in theGET /users
endpoint. - We changed the data type from array[integer] to array[string] in the request
id
field in thePUT /users/deactivate
endpoint.
Impacted endpoints:
- POST /users/bulk-load
- GET /users
- PUT /users/deactivate
2025.1, 2024.2_SP3
API | Major Version to which the Breaking Change was introduced |
---|---|
Master Data API | v3 |
Removed: request field shopItems.inventoryAccountingMethodCode
Impacted endpoint:
- POST /shopitems/bulk-load
2025.1, 2024.2_SP3, 2024.3
API | Major Version to which the Breaking Change was introduced |
---|---|
Master Data API | No change in version v2 |
Deprecated: In order to support Multi-edge and Multi-version (ansible scripts) the existing endpoints are depracated and new ones introduced.
- POST /api/stations/{stationNo}/sqlDb/initialPublication
- POST /api/stations/{stationNo}/multiVersion/restoreEdgeSync
- POST /api/v2/stations/{stationNo}/multiVersion/disableEdgeSync
- GET /stations/locationIdentification
2024.3
API | Major Version to which the Breaking Change was introduced |
---|---|
Master Data API | No change in version v2 |
Changed data types for parameters:
- We changed the data type from integer(int32) to integer(int64) for
methodOfPayments.inquiryNumber
field in theGET /methodOfPayments
andPOST /methodOfPayments/bulk-load
endpoint.
Impacted endpoint:
- GET /methodOfPayments
- POST /methodOfPayments/bulk-load
2024.1
API | Major Version to which the Breaking Change was introduced |
---|---|
Marketing API | v2 |
Validation changes. More restricted validation are implemented on backend side to ensure an offer cannot be added outside of the promotion or campaign validity period. Impacted endpoints:
- POST /offers,
- PUT /offers/external/{offerExternalId},
- PUT /offers,
- POST /campaigns/{offerId},
- PUT /campaigns/{campaignId}
2023.3_SP2
API | Major Version to which the Breaking Change was introduced |
---|---|
Master Data API | v2 |
New HTTP response code 206: "Partial Content" added.
Impacted endpoints:
- PUT /suppliers/deactivate,
- PUT /taxes/deactivate,
- PUT /timeRestrictions/deactivate
2023.3 SP1
API | Major Version to which the Breaking Change was introduced |
---|---|
Promotions API | v5 |
- Removed: not used properties from the request. Deleted parameters:
transaction.identifiedCustomer.stampcards.stampcardsToBeRedeemed.*
transaction.identifiedCustomer.stampcards.stampcardsToBeReleased.*
transaction.identifiedCustomer.pointsToBeGranted.*
transaction.identifiedCustomer.stampsToBeGranted.*
transaction.scannedCoupons.couponsToBeRedeemed.*
transaction.scannedCoupons.couponsToBeReleased.*
transaction.couponsAsBenefitToBeGranted.*
transaction.couponsAsBenefitToBeGranted.*
Impacted endpoints:
- POST /basket/calculation
- POST /basket/finalization
- Change: Data types for parameters modified
transaction.identifiedCustomer.grantedPointsToBeVoided.pointsCount
transaction.redeemedPointsToBeVoided.pointsCount
Impacted endpoint:
- POST /basket/void
2023.3
API | Major Version to which the Breaking Change was introduced |
---|---|
Customers API | v3 |
Resource modification. Changed endpoint path in EAPI, PAPI and SAPI.
Impacted endpoint:
- GET /customers/card/{cardNumber}
No change on backend side.
2023.2
API | Major Version to which the Breaking Change was introduced |
---|---|
Promotions API | v4 |
Change: data type for parameters modified. We have changed data type to the following response fields:
storedActions.voucherTemplateGettingActions.discountDetail.discountActionType
storedActions.couponValidityDatesCheckingActions.discountDetail.discountActionType
toBeFinalizeStoredActions.grantVoucherActions.discountDetail.discountActionType
toBeFinalizeStoredActions.grantMessageActions.discountDetail.discountActionType
Impacted endpoint:
- POST /basket/calculation
2023.2
API | Major Version to which the Breaking Change was introduced |
---|---|
Customers API | v2 |
Removed request field: movements.currencyId
Impacted endpoint:
- POST /accounts/{id}/movements