Pagination/Limit parameters for /odds/updated endpoint

I want to be able to control the amount of data returned by the /odds/updated endpoint using parameters like limit or pagination. Currently, it returns too much data at once, which is difficult to handle. This would help manage the data load and prevent "disasters" when processing large updates.