This endpoint helpfully breaks out hashtags into separate tables, which allows for some analysis. The results are similar for different endpoints, but may not match exactly. The renaming of the field suffixes (_u0 etc.) seems to change each time you run the wizard to generate your code. Presume there is an endpoint where you can enter a hashtag to follow this.
With the mapping of keys into tables it gives the ability to move this to have an incremental load, persisting old records. I've not got around to writing this yet.
Naturally I have stripped the connection from this app, so you will need to re-insert it. You will need to ensure you use the correct endpoint when you do this.