I wanted to circle back to this. It turns out we do actually expect to use a number, however there is a bug in type conversion. We’re fixing that soon. So the API Reference and Type files are correct, just not working as expected.
Sorry for the confusion. The SDK should accept both a string or a number, however currently if you pass in a number it rejects it. The type conversion in place is somehow bypassed. Our Engineering team is correcting this.