HTS Code Lookup avatar

HTS Code Lookup

Pricing

from $1.94 / 1,000 tariff lines

Go to Apify Store
HTS Code Lookup

HTS Code Lookup

HTS code lookup and US tariff schedule scraper: one row per line of the Harmonized Tariff Schedule with HTS code, description, unit of quantity, general, special and column 2 duty rates, and the rate a line inherits when it prints none. Each row names its edition. $2.00 per 1,000 tariff lines.

Pricing

from $1.94 / 1,000 tariff lines

Rating

0.0

(0)

Developer

Dami's Studio

Dami's Studio

Maintained by Community

Actor stats

0

Bookmarked

2

Total users

1

Monthly active users

6 days ago

Last modified

Features

Limited permissions

Share

HTS code lookup for chapters, codes or search terms, one row per line of the US tariff schedule: the HTS code, its description and full description path, the unit of quantity, the general, special and column 2 rates exactly as printed, the rate that applies when a line inherits it, and the edition it came from. It reads the US International Trade Commission's own published data.

The awkward part: an empty rate on a line does not mean duty-free.

InputChapters or chapter ranges, HTS codes at any depth, search terms, or the whole schedule
OutputOne row per tariff line: HTS code, description path, unit of quantity, general, special and column 2 rates as printed and as they apply, edition
Ceiling40,000 rows, 200 codes and 10 search terms per run
Account neededNone, and no API key
Price$2.00 per 1,000 tariff lines on the Free plan, a little less on paid plans. The free plan's $5 a month covers about 2,500

🔍 What HTS Code Lookup does

The edition is read before a single line, and every row carries it, so a dataset dates itself. It is read again at the end, and if a revision landed mid-run you get a free row saying so. On a schedule, requireEdition makes the run return nothing rather than a different edition.

Then the rates. The schedule states a rate once and lets the lines beneath it inherit, so a 10-digit line often prints nothing in its rate columns. In edition 2026HTSRev19, 11,836 of the 29,860 numbered lines carried no rate of their own. Read those blanks as zero and you price lines at no duty when they are dutiable. So each row keeps both readings apart:

FieldWhat it is
generalRate, specialRate, column2RateExactly what this line printed. null when it printed nothing
generalRateEffective, specialRateEffective, column2RateEffectiveThe rate that applies, copied verbatim from wherever it was stated
ratesAreInherited, rateSourceWhether it came from a line above, and the HTS code it was read off
dutyRateResolved, rateNotefalse when no line above prints a general rate, with the reason in plain words

A rate is only inherited from a line whose code starts the row's own code. Rates are never parsed into numbers. You get 15.9%, Free, 1¢/kg, 3.7¢/kg on drained weight, and in chapter 99 whole sentences such as The duty provided in the applicable subheading + 25%. Turning those into a number is a judgement about your goods.

Each chapter is checked before it is used. One that comes back empty, or carrying lines from another chapter, becomes a free row instead of a charge.

📋 What data you get from each tariff line

What you getField
The edition the row came fromhtsEdition, htsEditionTitle
The code, its level, and its chapter, heading and subheadinghtsno, lineLevel, chapter, heading, subheading
The line's own text, its heading's text, and the whole description pathdescription, headingDescription, descriptionPath, indent
The unit of quantity, as text and as a listunitOfQuantity, units
The general, special and column 2 rates as printedgeneralRate, specialRate, column2Rate
The rates that apply, and where they were read fromgeneralRateEffective, specialRateEffective, column2RateEffective, ratesAreInherited, rateSource, dutyRateResolved, rateNote
Extra duty provisions, and the publisher's footnotesadditionalDuties, footnotes
Which of your codes or terms picked the row, and the line on the USITC sitematchedQuery, htsUrl

▶️ How to scrape HTS codes and duty rates

  1. Open HTS Code Lookup and click Try for free.
  2. Type chapter numbers into Chapters, or clear it and use HTS codes or Search terms. The form arrives with chapter 61.
  3. Choose Which lines to return. "Statistical lines only" gives you the codes that go on an entry.
  4. Set Maximum rows, or tick Read the whole schedule and raise it to match.
  5. Click Start, then download the dataset as CSV, JSON or Excel, or read it from the Apify API.

💰 How much does it cost to scrape the tariff schedule?

$2.00 per 1,000 tariff lines, which is $0.002 a line on the Free plan, less on paid plans. On the free plan, the $5 Apify gives you each month covers about 2,500 lines. An average chapter holds around 300 lines, which comes to roughly 60 cents, and the whole schedule of about 29,900 lines to roughly $60.

You pay for tariff-line rows and nothing else per row. The sample row and every diagnostic row are free, including chapter 77, an empty chapter, a search term that finds nothing and a requireEdition refusal. Lines in chapters 98 and 99 that resolve to no rate are still charged, because they are still the lines you asked for. If you set a maximum charge on the run, it stops at that figure instead of going past it.

📥 What you give it

{
"hsCodes": ["8471.30", "6101.20"],
"searchTerms": ["olive oil"],
"includeLines": "statisticalOnly",
"maxItems": 200
}
FieldDefaultWhat it is
chaptersnone; the box starts at 61Chapter numbers 1 to 99, or ranges such as 61-63. 61 is knitted apparel, 84 machinery, 87 vehicles, 99 the temporary modifications. Chapter 77 is reserved and gets a free row saying so.
hsCodesnoneCodes at any depth, 2 to 10 digits, dots optional, up to 200. 8471 is a whole heading, 6101.20.00.10 one line.
searchTermsnoneWords looked up in the schedule's own index, up to 10. The index is broad: cotton shirt also finds cotton seed, so read the descriptions.
allChaptersfalseReads every chapter, 01 to 99. Raise maxItems to match or you get the first slice.
includeLinesallall, withDutyRate (8- and 10-digit lines only) or statisticalOnly (the 10-digit lines that go on an entry).
maxItems1001 to 40,000 rows.
requireEditionnone, which takes whatever is liveAn edition name such as 2026HTSRev20. If a different one is live, the run reads nothing and charges nothing.
proxyUrlsnoneYour own servers to send the traffic through, as http://user:pass@host:port. Leave it empty unless you need that.

One thing about combining them. Give chapters together with hsCodes or searchTerms and you get the whole chapters, with the codes only filling in matchedQuery. To get just the lines you named, leave chapters empty.

An input with nothing in it, such as {} sent through the API, returns one free sample row so you can see the shape first.

📤 What you get back

A real row from a run on 30 September 2026. Look at the rates: this line printed none, and the 15.9% it carries was read off 6101.20.00 above it.

{
"ok": true,
"charged": true,
"recordType": "tariffLine",
"htsEdition": "2026HTSRev20",
"htsEditionTitle": "Revision 20 (2026)",
"htsno": "6101.20.00.10",
"lineLevel": "statistical",
"chapter": "61",
"heading": "6101",
"subheading": "6101.20",
"headingDescription": "Men's or boys' overcoats, carcoats, capes, cloaks, anoraks (including ski-jackets), windbreakers and similar articles, knitted or crocheted, other than those of heading 6103:",
"indent": 2,
"description": "Men's (334)",
"descriptionPath": "Men's or boys' overcoats, carcoats, capes, cloaks, anoraks (including ski-jackets), windbreakers and similar articles, knitted or crocheted, other than those of heading 6103: > Of cotton > Men's (334)",
"unitOfQuantity": "doz., kg",
"units": ["doz.", "kg"],
"generalRate": null,
"specialRate": null,
"column2Rate": null,
"generalRateEffective": "15.9%",
"specialRateEffective": "Free (AU,BH, CL,CO,IL,JO,KR, MA,OM, P,PA,PE,S,SG)",
"column2RateEffective": "50%",
"ratesAreInherited": true,
"rateSource": "6101.20.00",
"dutyRateResolved": true,
"rateNote": null,
"additionalDuties": null,
"footnotes": [],
"matchedQuery": null,
"htsUrl": "https://hts.usitc.gov/search?query=6101.20.00.10",
"scrapedAt": "2026-09-30T02:28:10.927Z"
}
FieldHow to read it
htsEdition, htsEditionTitleThe edition the row came from, so two pulls a month apart can be told apart without notes.
htsno, lineLevelThe code as published, and its level: heading (4 digits), subheading (6), tariffLine (8) or statistical (10).
description, descriptionPathThe line's own text, often a fragment like Men's (334), and the whole branch joined with > so a deep line reads on its own.
unitOfQuantity, unitsThe published unit as text, and the same thing split into a list. Many lines carry two.
additionalDuties, footnotesExtra duty provisions, mostly chapter 99 safeguards, and the publisher's own footnotes, untouched.
matchedQueryWhich of your codes or search terms picked the row.
htsUrlThe line on hts.usitc.gov, for when someone wants to check.

🧾 Reading the output

Three kinds of row can share a dataset, and charged is the field that separates them.

RowHow to spot itCharged
A tariff linecharged: trueyes
The sample_sample: true, charged: falseno
A diagnostic_diagnostic: true, charged: false, an errorCodeno

The sample row also says recordType: "tariffLine", so filter on charged == true, not on recordType.

CodeWhat it means
NO_RESULTSSeveral cases, and details says which: nothing matched, a search term found nothing, chapter 77, a chapter that came back empty, a requireEdition that is not the live one, or a revision that landed while the run was reading.
BAD_INPUTSomething in chapters or hsCodes is not a chapter number or an HTS code.
NETWORKThe schedule could not be read. If that happens at the edition check, nothing is read at all.
TIME_BUDGETThe run ran out of time before a chapter was read.

💡 What people use it for

  • Checking the duty on a product before pricing an import, with the rate and the line it came from on one row.
  • Keeping your own history. Only the live edition is published, so a pull after each revision is the only archive you will have.
  • Seeing what a revision moved, by comparing two pulls on htsno plus generalRateEffective.
  • Loading the schedule into a spreadsheet, where descriptionPath makes a deep line readable on its own.

🚧 What it does not do

  • No classification. Which line your goods fall under is your call, or your broker's.
  • No advice, customs, legal or otherwise.
  • Only the live edition. There is no way to ask for last year's rates.
  • No notes. Chapter titles are not returned either.
  • Only the US schedule. No other country's tariff.
  • No duty calculation. No landed cost, freight, trade-remedy stacking or rules of origin.
  • Chapters 98 and 99 carry lines with no rate. In edition 2026HTSRev19, 1,169 of their lines resolved to no general rate, because the treatment comes from a note rather than a rate column. They arrive with dutyRateResolved: false and a rateNote.
  • It is not an official USITC tool. Dami's Studio is independent and is not affiliated with or endorsed by the USITC or anyone named here.

🧭 Which trade data scraper do you need?

If you wantUse
US tariff lines and duty ratesThis one
Who imports what, from US customs shipment recordsImportYeti Scraper
Wholesale products, price ranges and MOQs from suppliersAlibaba.com Scraper
US industrial suppliers by product and locationThomasnet Suppliers Scraper

❓ Questions people ask

What is the HTS?

The Harmonized Tariff Schedule of the United States: the codes every imported good is classified under and the duty attached to each. The US International Trade Commission publishes it.

How many lines are in the US tariff schedule?

In edition 2026HTSRev19 there were 29,860 numbered lines: 961 headings, 2,093 subheadings, 6,857 eight-digit lines and 19,949 statistical lines.

Can I get the Section 232 and 301 duties?

Chapter 99 holds the temporary modifications and it is included: {"chapters": ["99"]}. For those lines you often get the treatment as a sentence rather than a percentage.

How do I notice when duty rates change?

Schedule it, compare runs on htsno plus generalRateEffective to see what moved, and watch htsEdition for when a revision landed.

Do I need an account or an API key?

No. The schedule is public and nothing here needs a key.

Can I call it from code or connect it to an AI assistant?

The API tab has code for Python, JavaScript and the CLI. MCP clients like Claude and ChatGPT use https://mcp.apify.com/?tools=fetch-actor-details,dami_studio/hts-customs-duty-scraper; coding assistants can load our skill file. All three bill your Apify account at the same price.

The US International Trade Commission publishes the schedule openly, and this reads it with no login. Apify's write-up on the legality of web scraping covers the wider question, and we are not lawyers.

🆘 If something breaks

Open the Issues tab on the actor page and send the run ID with the input you used. The errorCode and details on a diagnostic row usually name the reason already.