Sales tax API example for ZIP 30301

The verified request

The zip parameter identifies the lookup area. The optional date parameter asks for the record effective on that day instead of whichever rate happens to be current when the request runs.

Selected response fields

The snapshot below contains selected response fields from the production result. Open the live JSON to inspect the complete current envelope.

{
  "api_version": "0.5.93",
  "zip_code": "30301",
  "state_code": "GA",
  "country_code": "US",
  "total_rate": 0.0775,
  "effective_period": "[2026-06-07,2026-06-08)"
}

Reproduce the sales tax API example

These requests use only standard HTTP clients. The public lookup is bounded for evaluation; production integrations should use an account API key and the limits assigned to that plan.

curl --fail-with-body --get \
  "https://taxautomator.net/api/v1/rates" \
  --data-urlencode "zip=30301" \
  --data-urlencode "date=2026-06-07"

const params = new URLSearchParams({
  zip: "30301",
  date: "2026-06-07",
});

const response = await fetch(
  `https://taxautomator.net/api/v1/rates?${params}`,
);

if (!response.ok) throw new Error(`HTTP ${response.status}`);
console.log(await response.json());

import json
import urllib.parse
import urllib.request

query = urllib.parse.urlencode({
    "zip": "30301",
    "date": "2026-06-07",
})
url = f"https://taxautomator.net/api/v1/rates?{query}"

with urllib.request.urlopen(url, timeout=10) as response:
    print(json.load(response))

What this result proves

It proves that a dated ZIP lookup can return a normalized location, decimal rate, effective period, and API version through a stable JSON contract. Keeping the date in the request makes the example repeatable even after newer records become active.

Important boundary: A ZIP-level rate is an estimate for workflows that do not yet have a validated street address. TaxAutomator does not determine nexus, product taxability, exemptions, filing obligations, or remittance, and ZIP codes can cross local tax boundaries.