This was indeed a bug and our development team just deployed an update to the API that should resolve the problem. Please give it another look and if anything looks incorrect or if you have any questions please feel free to contact our support team direct at support@myintervals.com.