@Anastasiia Ilina - The API response you pasted above are for spot pricing (highlighted below).
I did a quick check for the meter that has 0.234 price point in west US – and I think D4 v3 and D4s v3 both emit the same meterId. Meter Ids are reliable way to triangulate the price point for reconciliation point of view. Can you please explain what you are trying to do between the ACOM pricing experiences and the API response?
https://prices.azure.com/api/retail/prices?currencyCode=%27USD%27&$filter=armRegionName eq %27westus%27 and priceType eq %27Consumption%27 and retailPrice eq 0.234
{
"BillingCurrency": "USD",
"CustomerEntityId": "Default",
"CustomerEntityType": "Retail",
"Items": [
{
"currencyCode": "USD",
"tierMinimumUnits": 0,
"retailPrice": 0.234,
"unitPrice": 0.234,
"armRegionName": "westus",
"location": "US West",
"effectiveStartDate": "2017-07-21T00:00:00Z",
"meterId": "8462aa11-a392-4ae4-87cf-2dbabe31d487",
"meterName": "D4 v3/D4s v3",
"productId": "DZH318Z0BQ4K",
"skuId": "DZH318Z0BQ4K/00ST",
"productName": "Virtual Machines Dv3 Series",
"skuName": "D4 v3",
"serviceName": "Virtual Machines",
"serviceId": "DZH313Z7MMC8",
"serviceFamily": "Compute",
"unitOfMeasure": "1 Hour",
"type": "Consumption",
"isPrimaryMeterRegion": true,
"armSkuName": "Standard_D4_v3"
}
],
"NextPageLink": null,
"Count": 1
}