UPGRADE-API-2.1.md
2.1.14 TO 2.1.15GET /api/v2/shop/payment-requests/{hash}, PUT /api/v2/shop/payment-requests/{hash} and POST /api/v2/shop/orders/{tokenValue}/payment-requests now enforce ownership:
404 Not Found, unless the underlying order is a guest order. An order qualifies as a guest order when it has no customer, when its customer has no associated user account, or when it was placed through the guest checkout flow (Order::isCreatedByGuest() returns true).404 Not Found.Previously these operations could be performed by any authenticated user or even an anonymous user who knew the payment request hash (or, for the creation endpoint, the order token value), which constituted a broken object-level authorization (IDOR) vulnerability.
No action is required unless your integration assumed that these endpoints were publicly accessible or shared across customers.
Sylius\Bundle\ApiBundle\StateProvider\Shop\Payment\PaymentRequest\ItemProvider constructorA new UserContextInterface argument is appended to the constructor. Omitting it is deprecated and will be required in Sylius 3.0; without it the ownership check is skipped and the provider falls back to its previous behavior.
Sylius\Bundle\ApiBundle\CommandHandler\Payment\AddPaymentRequestHandler constructorA new, nullable UserContextInterface argument is appended to the constructor. When it is not provided, the ownership check is skipped and the handler falls back to its previous behavior.
2.1.10 TO 2.1.11Sylius\Bundle\ApiBundle\Serializer\ContextBuilder\PaymentRequestActionAwareContextBuilder:
public function __construct(
+ private readonly IriToIdentifierConverterInterface $iriToIdentifierConverter,
SerializerContextBuilderInterface $decoratedContextBuilder,
string $attributeClass,
string $defaultConstructorArgumentName,
)
2.1.4 TO 2.1.5The OrderItem response has been modified to include the variantName property.
"@context": "\/api\/v2\/contexts\/Order",
"@id": "\/api\/v2\/shop\/orders\/token",
"@type": "Order",
...
"items": [
{
"@id": "\/api\/v2\/shop\/orders\/token\/items\/XYZ",
...
"productName": "Mug",
+ "variantName": "Blue Mug"
...
}
...
2.0 TO 2.1Various admin and shop Order responses have been modified to include the checkoutCompletedAt
date and a promotionCoupon object. For the details of where these properties are available,
check the Order's serialization context.
"@context": "\/api\/v2\/contexts\/Order",
"@id": "\/api\/v2\/shop\/orders\/token",
"@type": "Order",
...
+ "promotionCoupon": {
+ "@id": "\/api\/v2\/shop\/promotion-coupons\/XYZ2",
+ "@type": "PromotionCoupon",
+ "code": "XYZ2"
+ },
+ "checkoutCompletedAt": null,
...
The shop responses of Product index and show have been modified to include the default variant as a serialized object under the defaultVariantData property.
"@context": "\/api\/v2\/contexts\/Product",
"@id": "\/api\/v2\/shop\/products\/product-code",
"@type": "Product",
...
"defaultVariant": "\/api\/v2\/shop\/product-variants\/MUG_BLUE",
+ "defaultVariantData": {
+ "@context": "\/api\/v2\/contexts\/ProductVariant",
+ "@id": "\/api\/v2\/shop\/product-variants\/MUG_BLUE",
+ "@type": "ProductVariant",
+ "name": "Blue Mug",
+ "inStock": true,
+ "price": 2000,
+ "originalPrice": 3000,
+ "lowestPriceBeforeDiscount": null
+ }
2 new groups have been added for the purpose of serializing of the default variant specifically:
A new compound filter has been added to the shop Product index endpoint to retrieve associated products of
either a product or/and an association type. The filter can be used by adding an association[ownerCode]
or association[typeCode] query parameter to the request.
Adding both at once will result in a logical AND operation, limiting the result to only products
associated with the given owner and within the association type.
GET /api/v2/shop/products?association[ownerCode]={example-product-code}&association[typeCode]={example-association-type-code}
A new index endpoint has been added to the shop to retrieve the list of available product options.
GET /api/v2/shop/product-options
Which results in:
{
"@context": "\/api\/v2\/contexts\/ProductOption",
"@id": "\/api\/v2\/shop\/product-options",
"@type": "hydra:Collection",
"hydra:totalItems": 2,
"hydra:member": [
{
"@id": "\/api\/v2\/shop\/product-options\/COLOR",
"@type": "ProductOption",
"code": "COLOR",
"name": "Color"
},
{
"@id": "\/api\/v2\/shop\/product-options\/SIZE",
"@type": "ProductOption",
"code": "SIZE",
"name": "Size"
}
],
"hydra:search": {
"@type": "hydra:IriTemplate",
"hydra:template": "\/api\/v2\/shop\/product-options{?productCode}",
"hydra:variableRepresentation": "BasicRepresentation",
"hydra:mapping": [
{
"@type": "IriTemplateMapping",
"variable": "productCode",
"property": "productCode",
"required": false
}
]
}
}
The result can be filtered by the productCode query parameter, which limits the
options to those that are available for the given product.
A new index endpoint has been added to the shop to retrieve the list of available product option values.
GET /api/v2/shop/product-option-values
Which results in:
{
"@context": "\/api\/v2\/contexts\/ProductOptionValue",
"@id": "\/api\/v2\/shop\/product-option-values",
"@type": "hydra:Collection",
"hydra:totalItems": 4,
"hydra:member": [
{
"@id": "\/api\/v2\/shop\/product-options\/COLOR\/values\/COLOR_BLUE",
"@type": "ProductOptionValue",
"code": "COLOR_BLUE",
"option": "\/api\/v2\/shop\/product-options\/COLOR",
"value": "Blue"
},
...
{
"@id": "\/api\/v2\/shop\/product-options\/SIZE\/values\/SIZE_LARGE",
"@type": "ProductOptionValue",
"code": "SIZE_LARGE",
"option": "\/api\/v2\/shop\/product-options\/SIZE",
"value": "Large"
}
],
"hydra:search": {
"@type": "hydra:IriTemplate",
"hydra:template": "\/api\/v2\/shop\/product-option-values{?productCode}",
"hydra:variableRepresentation": "BasicRepresentation",
"hydra:mapping": [
{
"@type": "IriTemplateMapping",
"variable": "productCode",
"property": "productCode",
"required": false
}
]
}
}
The result can be filtered by the productCode query parameter, which limits the
option values to those that are available for the given product,
regardless whether they're used within it's variants or not.
A new index endpoint has been added to the shop to retrieve the list of available association types.
GET /api/v2/shop/product-association-types
Which results in:
{
"@context": "/api/v2/contexts/ProductAssociationType",
"@id": "/api/v2/shop/product-association-types",
"@type": "hydra:Collection",
"hydra:totalItems": 20,
"hydra:member": [
{
"@id": "/api/v2/shop/product-association-types/similar-products",
"@type": "ProductAssociationType",
"code": "similar-products",
"name": "Similar Products"
},
...
{
"@id": "/api/v2/shop/product-association-types/accessories",
"@type": "ProductAssociationType",
"code": "accessories",
"name": "Accessories"
}
],
"hydra:search": {
"@type": "hydra:IriTemplate",
"hydra:template": "/api/v2/shop/product-association-types{?productCode}",
"hydra:variableRepresentation": "BasicRepresentation",
"hydra:mapping": [
{
"@type": "IriTemplateMapping",
"variable": "productCode",
"property": "productCode",
"required": false
}
]
}
}
Each of the returned product association types has at least one enabled associated product.
The productCode filter can be used to limit the association types to those that have an association with the given product set as the owner.