Changelog
Changes to the API, its documentation, and the rate data behind it.
Newest first.
Sefro has not made a breaking API change. Every endpoint documented since launch
still answers the same way. Breaking changes, if they ever become necessary, ship
under a new version prefix rather than altering
/v1 — see
Versioning.
November 14, 2026
Calculation
- FixTexas SaaS. Texas treats SaaS as a
data processing service and taxes 80% of the price.
saas line items in
Texas are now taxed on 80% of the price, and the other 20% is reported in
exempt_amount. /taxability returns the new
taxable_portion field.
- FixRegion names.
tax_region_name is no longer null. When the source data has no name, it is
built from the city, county and state, for example "Los Angeles, Los Angeles County, CA".
Data
- FixUtah and California refresh. Both states
changed the layout of their rate files for the October 1 quarter, and our daily refresh
stopped picking them up. It reads the new layouts now, so rates that changed on
October 1 are current again.
November 4, 2026
Calculation
- NewStreet-address rates. Send
to_street to /calculate, or street to
/validate/address. The address is geocoded to its county and city, so an
address whose ZIP is labeled with a neighborhood or a neighboring town gets the right
city tax, and an unincorporated address gets the county rate. Every calculation now
returns an address block with the method, confidence, and warnings.
- NewShipping. A
shipping
amount is taxed by the destination state's rule and reported in a
shipping block. total_with_tax includes it.
- NewOrigin sourcing. Send a ship-from
address (
from_zip and so on). In-state sales in AZ, IL, MS, MO, OH, TN, TX, UT
and VA are then taxed at the seller's location.
- FixGrocery rates in reduced-rate states no
longer drop local tax. AL, MO, MS and TN groceries were taxed at the state
grocery rate only. They now include county and city tax. Corrected rules: KS and AR
(state 0%, local tax applies), IL (1% local), UT (3% statewide), VA (1% local; we were
returning 0%), MS (5% state, cut from 7%).
- FixClothing. NY clothing at $110 and
over is now taxed; it was always treated as exempt. MA taxes only the amount over $175
per item, and RI only the amount over $250. VT clothing is exempt at any price. Each
line now returns its
taxable_amount.
- FixZIP plus city. When a ZIP holds
several jurisdictions, a supplied
to_city or to_county now picks
the matching one. It was ignored before.
September 17, 2026
Rate data
- DataRates now refresh daily instead of weekly.
The full fetch runs every day at 09:00 UTC, after midnight in every US time zone.
Previously it ran only on Sundays, so a rate taking effect on a quarter boundary
could be up to several days late. October 1 changes now apply on October 1.
- FixAlaska: ZIPs not covered by the
Alaska Remote Seller Sales Tax Commission were being given the statewide local
average of 1.82%. Anchorage and Fairbanks levy no sales tax and now correctly
return 0%, marked
estimated. Municipalities with a real local tax,
such as Juneau and Kenai, are unchanged and remain authoritative.
- FixNevada: the statewide 6.85% base
was being folded into the county component, so component breakdowns did not reflect
how Nevada levies the tax, and counties absent from the source file could publish a
combined rate below the state minimum. Components are now split correctly and no
row can fall below its state's base rate. Combined totals for covered ZIPs were
already correct and did not change.
- DataStatewide base rows restored.
GET /rates?state=XX and GET /rates/states now cover all
51 jurisdictions. Nevada had been missing.
API
- APIErrors are no longer metered.
Requests rejected for a client error, and any request that fails on our side, are
refunded to your monthly quota. Only requests we actually serve count. Quota 429s
are the one exception.
- APIZIP+4 accepted.
/rates and /calculate now take either a 5-digit ZIP or
ZIP+4, using the first five digits. A malformed ZIP returns a clear 400 instead of
a misleading "no rate found".
- APICounty lookups work.
?state=CA&county=Los+Angeles previously returned 404 in nearly
every state. It now resolves to the county-level rate and reports which ZIP row
answered.
- FixUnknown product categories are rejected.
A misspelled
category on a line item used to fall through to being
taxed at the full rate. It now returns 400 listing the valid categories.
Documentation
- DocsNew quickstart covering the
path from a fresh key to a recorded sale, with examples in curl, Python and
Node.js. See Quickstart.
- DocsNew Keys & security section
explaining why API keys must stay server-side and why browser calls are blocked by
design. See Keys & security.
- DocsTransactions, Reports and Usage are now
documented. These endpoints already existed but were missing from the
reference.
- DocsVersioning guidance: pin new
integrations to the
/v1 prefix.
- FixThe
/rates example response had
components that did not sum to its stated total, and labelled an estimated source
as authoritative. Replaced with real API output, plus a table explaining what
rate_type, effective_date, updated_at and
all_jurisdictions actually mean.
- DocsRate-limit and request-id response headers are
now documented, along with the base URL
api.sefro.app, which had been
shown inconsistently.
September 6, 2026
- FixIncorrect statewide rates on state guide
pages. Nevada, Alabama, Idaho and New Mexico published wrong base rates,
derived from an unreliable column rather than an authoritative table. Corrected,
with a validation guard so a missing or zero base can no longer be published.
- APIAccount page added for usage,
billing management and self-serve API-key re-issue.
- APITrial entitlement enforced at the
advertised 10,000 requests, tracked separately from the plan quota it converts to.
- DocsPricing, quotas and plan figures aligned across
the site, documentation and checkout.
September 1, 2026
- API
GET /usage — check
your own consumption, remaining allowance, overage and reset date.
- APISelf-serve key re-issue. Replace a
lost or exposed key without contacting support; the old key stops working
immediately.
← Back to documentation