Different REST representations of the same resource - json

Question

I have a following situation when designing Rest.
For example I have a list of daily prices
[
{"id": 50,
"date": "2018-01-05"},
{"id": 60,
"date": "2018-01-06"},
{"id": 70,
"date": "2018-01-10"}
]
First I want to get all the prices in certain period, for example in January with GET /prices/?startDate=2018-01-01&endDate=2018-01-31 and it would return the results as seen above.
Secondly I want to get prices for the the same period but with price=0 where no price exists, such as
[
{"price": 50,
"date": "2018-01-05"},
{"price": 60,
"date": "2018-01-06"},
{"price": 0,
"date": "2018-01-07"},
{"price": 0,
"date": "2018-01-08"},
{"price": 0,
"date": "2018-01-09"},
{"price": 70,
"date": "2018-01-10"},
{"price": 0,
"date": "2018-01-11"}
]
Could I go with a new endpoint for this such as /prices/in-range/?startDate=2018-01-01&endDate=2018-01-31.
Would that be misleading? Should REST return data that is non-existing such as price=0, or should it be left to client to maniuplate original data?
Is there a naming convention in REST for "derived" data from one resource to another? I am not choosing what data to display, I am basically creating new data here.