# /us_hts/lines

`POST /api/us_hts/lines`

Price: 1 credit

Get US Harmonized Tariff Schedule lines for one HTS code — duty rates, units of quantity, quota quantity, additional duties and footnotes

## How to use it

Use this when you already have an HTS code and want the US import duty for it. The code may be given at any level and the answer covers that code and everything below it, so 0901.11 returns the 8- and 10-digit lines beneath it rather than a single row. Duty is split three ways: general_rate is the rate for normal trading partners, special_rate names the preference programmes in brackets, and other_rate is the column 2 rate for countries without normal trade relations; an empty rate on a row means the rate sits on a line further down. Rows where is_group_caption is true are headings that group the rows after them and carry no code of their own. A 2-digit chapter number is rejected — list a whole chapter with us_hts/chapters/lines. count trims the subtree; the largest heading in the schedule, 9902, returns 1655 rows, so pass a count above that to be sure of getting the whole subtree under hts_number.

## Parameters

- `access-token` (string, required)

## Request body

- `timeout` (integer) — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
- `hts_number` (string, required) — HTS code at heading (4 digit), subheading (6 digit), tariff (8 digit) or statistical (10 digit) level, with or without dots, or an hts.usitc.gov search URL (examples: "0901.11.00.15", "8471.50", "0901", "https://hts.usitc.gov/search?query=8703.80.00"; minLength: 1)
- `count` (integer, required) — Max number of lines to return (min: 1)

## Response

### 200 — Successful Response

- `@type` (string) (default: "UsHtsLine")
- `hts_number` (string) (default: "")
- `description` (string, required)
- `indent` (integer, nullable)
- `is_group_caption` (boolean) (default: false)
- `units` (array) (default: [])
- `general_rate` (string, nullable)
- `special_rate` (string, nullable)
- `other_rate` (string, nullable)
- `quota_quantity` (string, nullable)
- `additional_duties` (string, nullable)
- `footnotes` (array) (default: [])
  - `@type` (string) (default: "UsHtsFootnote")
  - `value` (string, required)
  - `marker` (string, nullable)
  - `columns` (array) (default: [])
  - `footnote_type` (string, nullable)

## Errors

### 422 — Validation Error

The request body did not validate

What to do: Check the fields against this schema. A URN with the wrong prefix is the most common cause.

- `detail` (array)
  - `loc` (array, required)
  - `msg` (string, required)
  - `type` (string, required)
  - `input` (any)
  - `ctx` (object)

### 408

The request ran past its time limit

What to do: Raise `timeout` in the request body, up to the maximum this endpoint documents. Lowering `count` or turning off the `with_*` flags also helps, because less work finishes sooner.

### 412

The HTS code carries no line in the current revision of the tariff schedule

What to do: Retrying will not help: either the entity does not exist, or the input points at a different one.

### 429

Too many requests: a rate limit or a usage window is exhausted

What to do: When the response carries an X-Retry-After header, wait that many seconds and retry: the same number is in the body as `detail.retry_after`, and the limit clears once that window passes. The message in the body names the limit that was hit.

### 500

Something broke on our side

What to do: Retrying will not help. If it keeps happening, send us the X-Request-ID from the response headers.

### 529

Rate limit reached, or the endpoint is overloaded

What to do: Wait at least 30 seconds, then retry.

## Response envelope

Success: Array of objects (may be empty if no results)

Error: Error may coexist with partial results if it occurs mid-execution. Check X-Error header and status code.

Every response carries these headers:

- `X-Error` — Error message text (present only on error)
- `X-Request-ID` — Unique request identifier
- `X-Execution-Time` — Execution time in seconds
- `X-Result-Count` — How many records the body carries. 0 means an empty result, which is a normal answer and not by itself an error. A non-zero count can come back together with X-Error when the failure happened partway through — read this header and X-Error independently.
- `X-Total-Available-Results` — How many records exist for this query, when the endpoint can say. On a `dry_run` request this is the answer and the body is empty. It saturates: the endpoint's documented maximum means 'at least that many', any smaller number is exact.
- `X-Warning` — Present when the request body carried keys this endpoint does not document. They were ignored, so any filter you meant to apply through them did not apply. Check the spelling against this schema and retry.
- `X-Retry-After` — Seconds to wait before retrying. Present only on 429.