US Tariff Scraper - US Import Tariff API, HTS Codes & Duty avatar

US Tariff Scraper - US Import Tariff API, HTS Codes & Duty

Pricing

from $11.10 / 1,000 tariff lines

Go to Apify Store
US Tariff Scraper - US Import Tariff API, HTS Codes & Duty

US Tariff Scraper - US Import Tariff API, HTS Codes & Duty

For importers, customs brokers and landed-cost tools: official USITC tariff lines with duty rates as numbers you can calculate with. 10-digit statistical lines come back with a rate - in the raw schedule all 35 lines under heading 6109 are blank. No API key.

Pricing

from $11.10 / 1,000 tariff lines

Rating

0.0

(0)

Developer

NeverEmpty

NeverEmpty

Maintained by Community

Actor stats

0

Bookmarked

2

Total users

1

Monthly active users

2 days ago

Last modified

Share

US Import Tariff API - HTS Codes, Duty Rates & Customs Tariff

For importers, customs brokers and landed-cost models: the official US Harmonized Tariff Schedule (USITC) as rows with the duty rate already parsed into a number you can multiply, the full product description rebuilt from the tariff hierarchy, and the trade programs that enter duty free.

In the raw schedule, the lines you actually import have no rate at all. Measured on 2026-09-01: in heading 6109 (T-shirts) all 35 ten-digit lines are blank, and in 0901 (coffee) 29 of 31 — the rate lives on the 8-digit parent. This Actor carries it down and records where it came from, so 6109.10.00.04 comes back with 16.5% instead of nothing. A run on 2026-09-01 over 5 codes plus the keyword espresso returned 20 tariff lines in 3.1 seconds, with 0 rows carrying an empty duty rate and 13 rates inherited from an 8-digit parent.

It never puts a number in a column it could not read. Chapter 99 lines read "The duty provided in the applicable subheading + 25%" — 471 of the 628 chapter 99 lines are in that shape (2026-09-01) — and those come back with the original text kept and the numeric fields null, rather than a 25 that would hide the base rate.

Look up by HTS number (4, 6, 8 or 10 digits) or by keyword. No API key, no page scraping, no proxy — US government data, public domain. Export as JSON, CSV or Excel.

  • Both the parsed values and the original text are in every row, so nothing is hidden behind a guess.

What this returns that the raw USITC data does not

ColumnWhy it matters
generalRateText on 10-digit lines🔴 In the raw schedule, 10-digit statistical lines have an empty rate. Measured on 2026-09-01: in heading 6109 (T-shirts) all 35 ten-digit lines are blank, in 0901 (coffee) 29 of 31. The rate lives on the 8-digit subheading. This Actor carries it down and records rateInheritedFrom, so 6109.10.00.04 comes back with 16.5% instead of nothing.
fullDescriptionThe raw description of 0901.11.00.15 is just "Certified organic". Here it is Coffee, whether or not roasted... > Coffee, not roasted > Not decaffeinated > Arabica > Certified organic, rebuilt from the indent levels.
generalAdValoremPercent, generalSpecificRates"16.5%" becomes 16.5; "33.9¢/kg + 5.1%" becomes a 5.1% rate plus a 33.9 US cents per kg amount; "$1.104/kg" is kept as dollars. 🔴 If any part of the text cannot be read, every numeric field stays null and the whole text goes to generalUnparsed. Chapter 99 lines read "The duty provided in the applicable subheading + 25%": putting 25 in the percent column would hide the base rate, and "... +0%" would read as duty free. Measured on 2026-09-01, 471 of the 628 chapter 99 lines are in that shape.
specialFreePrograms, specialClausesThe special column is written as Free (A,AU,BH,...)8.8¢/liter(JO) - clauses with no separator between them, and stray spaces inside the code list. This splits it into clauses and gives you the sorted list of programs that enter duty free, so "is my country free under this line?" is one lookup.
otherRateText, otherAdValoremPercentColumn 2 (non-normal-trade-relations) rates, parsed the same way.
units, footnotes, quotaQuantity, additionalDutiesKept as they are. USITC misspells one of these fields in its own JSON (addiitionalDuties); both spellings are read.

Input

FieldTypeDefaultMeaning
codesarraynoneHTS numbers with 4, 6, 8 or 10 digits, dots optional. Each returns the lines under it. Only when both codes and keyword are empty does the run use the example 0901 (coffee), and every row then says so in note. The input form opens with that example filled in: if codes is exactly ["0901"] and you typed a keyword, the example is treated as left over and skipped (one skipped row, not charged, says so).
keywordstring""Search the schedule, for example "espresso" or "t-shirts". USITC's own search returns a line if any of your words appears anywhere, including the unit: t-shirts comes back with 405 lines, most of them measured in t (tons), such as sugar beet. USITC's search also returns only the first line under a matching heading row (under "Other T-shirts:" it returns Men's but not Boys' 6109.10.00.14). This Actor reads every heading the search touches (including headings it only touched through a 4 or 6 digit heading row, such as 0103 Live swine for swine), rebuilds the full description of every line in it, and delivers every line whose full description (its own words plus the headings above it) contains every word you typed and that carries a duty rate, so a word that matches a heading brings back all the lines under it. Lines come in this order: headings whose own title contains your words first (for cotton, chapter 52), then headings where a 6-digit subheading does, then the rest, each group in HTS order. Plurals and hyphens are treated alike (t-shirts, T-shirt and t shirts are the same search, and so are knife and knives); a keyword that is an HTS number matches by number. maxRowsPerCode also caps a keyword search; the lines it cut, and their headings, are listed in the not-delivered row.
includeHeadingsbooleanfalseOff: only 8 and 10 digit lines, the ones that carry a rate. On: also the headings and wording rows.
maxRowsPerCodeinteger500Upper bound per code so a whole chapter cannot run up a bill.
maxRetriesinteger4Retries when USITC does not answer.

Output

{
"rowType": "tariff-line",
"requested": "6109.10.00.04",
"htsNumber": "6109.10.00.04",
"fullDescription": "T-shirts, singlets, tank tops and similar garments, knitted or crocheted > Of cotton > Men's or boys' > ...",
"generalRateText": "16.5%",
"generalAdValoremPercent": 16.5,
"generalIsFree": false,
"rateInheritedFrom": "6109.10.00",
"specialFreePrograms": ["AU", "BH", "CL", "CO", "IL", "JO", "KR", "MA", "OM", "P", "PA", "PE", "S", "SG"],
"otherRateText": "90%",
"otherAdValoremPercent": 90,
"units": ["doz.", "kg"]
}

What it does when something is wrong

  • A number with no lines under it → one row saying so, not charged, and the run does not fail.
  • USITC answering with its web page instead of data (its API returns the single-page app for some paths) → an error row with the reason. It is never reported as "no tariff lines".
  • One code failing while the others work → the working rows are delivered and the failure is reported in its own row and in RUN_ISSUES.
  • A rate written in a form this Actor cannot parse → the numbers stay null and the text is kept in generalUnparsed / specialUnparsed. Nothing is silently rounded to zero or called duty free.
  • The same line asked for twice (0901 and 0901.11 in one run) is delivered and charged once.
  • A keyword hit that cannot be delivered properly is not delivered and not charged: lines that match your words but have no duty rate in USITC (for example chapter 98 and 99 provisions whose general rate is blank), lines whose heading could not be read, and lines beyond maxRowsPerCode. One not-delivered row (not charged) lists how many and which.
  • A run that hits the maximum total charge you set says so in the log and in RUN_BUDGET_STOP.
  • If nothing at all could be read and something failed, the run fails instead of finishing green.

Measured

Run on 2026-09-01 with 5 codes (two 10-digit lines, a 6-digit subheading, a chapter 99 surcharge line, a number with no lines) plus the keyword espresso: 20 tariff lines + 1 "no lines" row in 3.1 seconds, 6 headings fetched, 0 rows with an empty duty rate, 13 rates inherited from an 8-digit parent, 1 rate left unparsed with its text kept, 0 duplicate lines.

The build is covered by 77 automated checks, and 105 deliberate defects were injected one at a time to confirm those checks actually catch them.

Billing

Pay per event: one charge per tariff line delivered. The "no lines" row, the "not-delivered" row and rows that report a problem are not charged. A keyword search with a broad word (cotton, steel) returns hundreds of lines, up to the default maxRowsPerCode of 500 (at $0.015 per line, about $7.50). Try a small maxRowsPerCode first, or narrow the search with HTS numbers. Headings without a rate are hidden by default, so a lookup of one code costs the lines you asked about and nothing else.

Support

Questions and bug reports: use the Issues tab on this Actor. Include the input you ran and the run id.

Data source: USITC Harmonized Tariff Schedule — official US government data, public domain. This Actor is not affiliated with USITC or CBP. Tariff classification is a legal determination; use this data to prepare and check work, not as a customs ruling.