{"type":"video","version":"1.0","html":"<iframe src=\"https://www.loom.com/embed/9cd82653bacb4528bdaac117ec85a976\" frameborder=\"0\" width=\"1280\" height=\"960\" webkitallowfullscreen mozallowfullscreen allowfullscreen></iframe>","height":960,"width":1280,"provider_name":"Loom","provider_url":"https://www.loom.com","thumbnail_height":960,"thumbnail_width":1280,"thumbnail_url":"https://cdn.loom.com/sessions/thumbnails/9cd82653bacb4528bdaac117ec85a976-00001.gif","duration":114.29960590900001,"title":"Carves Bug and Pagination Params [DONT KEEP]","description":"In this video, I discuss a bug I encountered in the FleetCarves endpoint while working with pagination parameters. I demonstrate how adding pagination parameters affects the results and highlight an issue with the \"after\" parameter. Additionally, I mention a separate SQL issue that is not related to this particular check-in. Overall, the changes made to the REST API are mostly stylistic."}