Thanks for your patience and input. Changing the sExchange is good idea, but would be hard to do for backwards compatibility's sake. With this API, it is almost not worth changing too much because there will always be inherint limitations, which is why the new API is being developed, but will review your suggestions with the engineering team. I personally think the new API will be able to handle everything that you are looking to do and will also provide more data types.
Comment