matched- FloridaState6.00%
- DuvalCounty1.50%
taxRate: 0.0757.50%Complete answer
Every named jurisdiction has a valid current rate. taxRate holds their sum.
| Jurisdiction | Rate |
|---|---|
| ColoradoState · Sales | 2.90% |
| Denver, City and CountyCity · Sales | 5.15% |
| Colorado RTDSpecial district · Sales | 1.00% |
| Scientific and Cultural Facilities DistrictSpecial district · Sales | 0.10% |
Sample response. Boundaries: US Census Bureau.
curl https://netamount.com/rate/lookup \
-H "Authorization: Bearer $NET_AMOUNT_KEY" \
-H "Content-Type: application/json" \
-d '{"address":"1437 Bannock St, Denver, CO 80204, USA"}'{
"status": "matched",
"taxRate": 0.0915,
"jurisdictions": [
{ "name": "Denver, City and County", "rates": [{ "rate": 0.0515 }] },
{ "name": "Colorado RTD", "rates": [{ "rate": 0.01 }] },
{ "name": "Scientific and Cultural Facilities District", "rates": [{ "rate": 0.001 }] },
{ "name": "Colorado", "rates": [{ "rate": 0.029 }] }
]
}A wrong rate costs more than no rate. We return a total only when every named jurisdiction has a valid current rate.
matchedtaxRate: 0.0757.50%Every named jurisdiction has a valid current rate. taxRate holds their sum.
missing_ratestaxRate: nullNot availableA named jurisdiction has no rate on file. We return null, never zero.
ambiguoustaxRate: nullNot availableThe point sits on a shared boundary. We return null instead of a guess.
Send a full street address or a latitude and longitude. One endpoint handles both.
Addresses must resolve to one precise Google Maps rooftop match. We never pick the first of several.
State, county, city, and special district boundaries that contain the point, returned by name.
Lookups run against stored jurisdiction geometry, with holes and multipart shapes intact.
Each jurisdiction lists its current Sales rate components, so you can see how the total adds up.
When a rate is missing or a point sits on a shared edge, taxRate is null and status explains why.
Create, list, and revoke keys from the dashboard. We show each key once and store only a hash.
60 requests per minute with a burst of 10. A 429 response tells you how long to wait.
Sign in, create an API key, and send your first lookup in minutes.