This inconsistency will be resolved with our next API release. For more information, check out the patch notes here and further discussion here.