Doesn't provide access to all jurisdiction information about taxjar-ruby HOT 1 CLOSED

Hi @andrewhavens, thanks for taking the time to share your use case and specific examples of jurisdictions that go beyond a 1-to-1 pairing. The jurisdiction names we now return in our tax endpoint simply mirror our rates endpoint because developers wanted to display the names in a simplified tax breakdown without making multiple API requests.

Ideally, we'd expose more jurisdiction data down to the district level and return multiple jurisdiction parts where applicable. We handle this data for our own internal reporting and filing software, but we'd have to invest more time in our API to make this data accessible. I'll share your feedback with our team and use it for reference later when we decide to prioritize improvements.

from taxjar-ruby.