DEV Community: rmccharles

The IEEPA Era Is Over

rmccharles — Sun, 15 Mar 2026 20:18:25 +0000

Three weeks ago, the US tariff landscape changed more dramatically than at any point in the past year. If you move goods across the US–Canada border and haven’t had time to work through the implications, this issue is for you.

Here’s what happened, what it means, and what’s coming next.

What Happened

On February 20, 2026, the US Supreme Court ruled 6–3 in Learning Resources, Inc. v. Trump that the International Emergency Economic Powers Act (IEEPA) does not authorize the president to impose tariffs. Within hours, President Trump signed an executive order terminating all IEEPA-based tariffs, effective February 24 at 12:00am ET.

This ended the tariff regime that had been in place since March 2025 — including the 25% tariffs on Canadian goods and the so-called “Liberation Day” reciprocal tariffs on most other countries.

What Replaced It (Immediately)

One minute after IEEPA tariffs terminated, a new 10% global import surcharge took effect under Section 122 of the Trade Act of 1974. Key facts about Section 122:

Rate: 10% on all countries (Trump has signalled intent to raise to 15%, not yet implemented as of this writing)
Expiry: 150 days from February 24 — expires approximately July 23, 2026, unless extended by Congress
Canada/Mexico exception: CUSMA/USMCA-qualifying goods are exempt. If your goods meet CUSMA origin rules, the 10% does not apply.
Section 232 exception: Goods already subject to Section 232 tariffs (steel, aluminum, autos, copper, timber, lumber) are excluded from the 10% surcharge — but the Section 232 duties themselves remain fully in effect.
Section 301 exception: Existing Section 301 tariffs on Chinese goods are unaffected and remain in force.

For most CUSMA-compliant Canadian exporters to the US: the effective tariff picture improved significantly on February 24. Goods that previously faced a 25% IEEPA tariff now face 0% (if CUSMA-qualifying) or 10% (if not).

What’s Coming Next
Section 122 is a temporary bridge. On March 11, the USTR launched new Section 301 investigations targeting over 15 countries — including China, Mexico, the EU, Vietnam, South Korea, and others — for “structural excess capacity and production in manufacturing sectors.” Canada was not named in the initial round.

Section 301 investigations take months — public comment periods, hearings, USTR findings — before any tariffs can be imposed. Treasury Secretary Bessent has predicted tariffs will return to pre-ruling levels by August 2026. The most likely sequence: Section 122 expires in July, Section 301 tariffs kick in around the same time for the named countries.

The CUSMA review — the scheduled renegotiation of the US–Canada–Mexico trade agreement — is ongoing in parallel. The outcome of that review will significantly shape Canada’s long-term tariff exposure.

The Refund Question
The Supreme Court ruling did not address refunds of IEEPA tariffs already paid. The court acknowledged it would be a “mess.” CBP has been ordered to re-liquidate unliquidated entries without IEEPA duties, but the refund process for liquidated entries is being litigated. If your business paid significant IEEPA duties on Canadian or other imports in 2025 and early 2026, this is worth reviewing with your customs broker. File a protest to preserve your refund rights while the process plays out.

What This Means for Compliance Teams
Three practical actions worth taking this week:

Verify your CUSMA origin documentation. The exemption from the 10% Section 122 surcharge hinges on CUSMA qualification. If your certificates of origin are outdated or your classification has changed, you may be paying 10% unnecessarily.
Audit any goods subject to Section 232. Steel, aluminum, auto parts, copper, timber, and lumber face their own duty stack that is entirely separate from the IEEPA-to-Section 122 transition. These have not changed and will not be refunded.
Plan for July. Section 122 expires in approximately 130 days. Section 301 tariffs on the named countries are likely to be in place by then. If you source from China, Mexico, the EU, or any of the 15+ named economies, build that scenario into your Q3 cost planning now.

The Data Picture
For those tracking HTS codes: as of this week, the TradeFacts.io nightly diff shows no structural changes to the US HTS schedule since the ruling. The MFN rates and special program rates in the schedule itself are unchanged — the Section 122 surcharge applies on top of existing rates via a separate proclamation, not as a change to the tariff schedule. This means your classification-based rate lookups remain valid; the additional 10% is an overlay.

On the Canadian side: one minor CBSA code removal was detected in early March (a legacy yarn classification). The 2026 CBSA schedule is otherwise stable. CUSMA preferential rates (the UST column in the Canadian tariff) are unaffected.

About Tariff Wire
Tariff Wire is a free weekly digest of US & Canadian tariff changes, published by TradeFacts.io — the only API combining live US HTS and Canadian Customs Tariff data with nightly change detection. If someone forwarded this to you, subscribe free here.

How to Get US and Canadian Tariff Data via API (The Complete Developer Guide)

rmccharles — Sat, 14 Mar 2026 17:50:29 +0000

If you're building anything that touches cross-border trade — a landed cost calculator, a customs compliance tool, a Shopify app that shows import duty rates — you're going to need programmatic access to tariff data. This guide walks through every option, including the free government APIs, their limitations, and what to do when those limitations matter.

The data sources

There are two datasets you need for US/Canada cross-border work:

US Harmonized Tariff Schedule (HTS) — maintained by the US International Trade Commission (USITC). 32,295 records covering every importable product category.
Canadian Customs Tariff — maintained by the Canada Border Services Agency (CBSA). 22,461 records including MFN rates and preferential rates under CUSMA (the successor to NAFTA).

Both are public. Neither is particularly developer-friendly out of the box.

Option 1: The USITC REST API (free, US only)

The USITC publishes a REST API at hts.usitc.gov. It's real data and it's free. Here's how to use it:

Search by keyword

import requests

resp = requests.get(
    "https://hts.usitc.gov/reststop/api/details/sectionJSON",
    params={"query": "aluminum", "offset": 0, "limit": 20}
)
data = resp.json()

for item in data.get("HTSDetails", []):
    print(item["htsno"], item["description"], item["general"])

Lookup by HTS code

resp = requests.get("https://hts.usitc.gov/reststop/api/details/htsnoJSON/0101.30.00.00")
detail = resp.json()
print(detail["htsno"])       # 0101.30.00.00
print(detail["description"]) # Asses
print(detail["general"])     # 6.8%
print(detail["special"])     # Free (A+,AU,BH,CL...)

Get an entire chapter

resp = requests.get("https://hts.usitc.gov/reststop/api/details/sectionJSON",
    params={"query": "chapter:84", "limit": 500})

This works. The data is accurate. But there are real limitations you'll hit quickly.

Where the USITC API falls short

No Canadian data. The USITC API covers US imports only. If you need to show what a US exporter pays when shipping into Canada — the CUSMA/UST preferential rate, the MFN rate, the over-quota rate on dairy — you're on your own. The CBSA publishes the Canadian tariff as a PDF and an Excel file. There is no CBSA REST API.

No change detection. The USITC updates the HTS schedule — sometimes significantly, especially in a volatile tariff environment. The API doesn't tell you what changed. If you cache HTS data (and you should, for performance), you have no reliable signal for when to invalidate your cache.

Schema instability. The USITC has changed its API response format without notice. If you build a production integration directly on it, plan to babysit it.

No SLA. It's a government endpoint. It goes down. There's no uptime commitment.

Rate limits are unpublished. Hammer it and you'll get throttled, with no clear documentation on what the limits are.

For a side project or internal tool, these tradeoffs are often fine. For a production integration where your customers depend on rate accuracy, they're not.

Option 2: Parsing the CBSA Canadian Tariff yourself

The CBSA publishes the Canadian Customs Tariff as a downloadable Excel file each year. Here's how to parse it in Python:

import requests
import openpyxl
from io import BytesIO

url = "https://www.cbsa-asfc.gc.ca/trade-commerce/tariff-tarif/2026/html/tblmod-1-eng.xlsx"
resp = requests.get(url)
wb = openpyxl.load_workbook(BytesIO(resp.content), data_only=True)
ws = wb.active

records = []
for row in ws.iter_rows(min_row=2, values_only=True):
    tariff_code, description, mfn_rate, ust_rate = row[0], row[1], row[3], row[8]
    if tariff_code:
        records.append({
            "tariff": str(tariff_code),
            "description": description,
            "mfn": mfn_rate,
            "ust": ust_rate,
        })

print(f"Loaded {len(records)} records")

This works — once. The problems start when you need to maintain it:

The CBSA changes the Excel column layout between releases without documentation
The file URL changes each year
Supply management goods (dairy, poultry) have over-quota rates of 200–400% that need special handling
There are 6,229 duplicate records where .00 suffix variants exist alongside base codes
You're now responsible for storing, serving, and updating this data in your application

Option 3: Use a purpose-built tariff API

If you need both US HTS and Canadian Customs Tariff data with a stable schema and change detection, TradeFacts.io is a REST API built specifically for this. It pulls nightly from USITC and CBSA, normalizes both datasets into consistent JSON, diffs each nightly run to detect changes, and delivers webhook alerts when rates change.

import requests

headers = {"X-API-Key": "your_api_key"}

# US HTS lookup
resp = requests.get("https://tradefacts.io/api/hts/0101.30.00.00", headers=headers)
print(resp.json())

# Canadian tariff lookup
resp = requests.get("https://tradefacts.io/api/ca/0401.10.10", headers=headers)
print(resp.json())

# Search CA dataset
resp = requests.get("https://tradefacts.io/api/ca/search", params={"q": "dairy"}, headers=headers)

# What changed in the last 7 days?
resp = requests.get("https://tradefacts.io/api/changes", params={"days": 7}, headers=headers)

No-auth demo endpoint for evaluation:

curl "https://tradefacts.io/api/demo/search?q=steel&ds=us"
curl "https://tradefacts.io/api/demo/search?q=dairy&ds=ca"

30-day free trial at tradefacts.io — no credit card required.

Choosing the right approach

	USITC API	CBSA Excel	TradeFacts.io
US tariff data	✓	✗	✓
Canadian tariff data	✗	✓ (manual)	✓
Change detection	✗	✗	✓
Webhook alerts	✗	✗	✓ (Pro)
Schema stability	✗	✗	✓
Uptime SLA	✗	✗	✓
Cost	Free	Free	Paid

If you only need US data for a low-stakes integration: use the USITC API directly. If you need Canada, need both, or are building something production-critical: the maintenance cost of rolling your own will exceed the API cost fairly quickly.

Conclusion

Tariff data is genuinely messy infrastructure. The government sources are authoritative but not production-ready. If you're building something that needs to stay current as rates change — especially with the current pace of tariff policy changes — plan for that maintenance cost up front rather than discovering it six months in when a client's landed cost calculations are wrong.