Call it what people search for
Why the tariff endpoint moved from /hts to /tariff while the code in its response is still called hts.
The tariff lookup started at /hts, named after the US Harmonized Tariff Schedule it reads. That was accurate, but I changed the route to /tariff because the route also has to help someone recognize the product.
If you're looking for a tariff lookup, /tariff tells you you're in the right place. You can learn the schedule's terminology as you need it, instead of having to know the abbreviation before finding the API.
The request now looks like this:
GET /tariff/8471.30.01.00
The response still calls the code hts. That wasn't renamed, because it describes the identifier you supplied. The route names the lookup. The field names the value. Making those two words identical would be tidier on paper and less precise in the response.
This isn't a rule against acronyms. VIN, IBAN, VAT, and IP are the terms people already use for those inputs. Spelling them out in a URL would add work without helping anyone. The question is whether the abbreviation is the word someone looking for the product would actually use.
The change also puts the page and SDK method under the same name: /tariff and parse.tariff(...). The old /hts API route was removed. If you used the original route, the URL needs updating. The hts field you read from its response stays the same.