> For the complete documentation index, see [llms.txt](https://docs.terminal.africa/tship/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.terminal.africa/tship/hs-codes-1.md).

# Simplified HS Codes

The HS Codes API allows you get accurate description to use for your shipment item

### The Simplified HS Code Object

This section describes the different attributes available for a HS Code.

| category           | *string* | Simplified category name                 |
| ------------------ | -------- | ---------------------------------------- |
| category\_code     | *string* | 4 digit category code                    |
| chapter            | *string* | 2 digit chapter code                     |
| chapter\_name      | *string* | Simplified chapter name                  |
| hs\_category\_code | *string* | 4 digit hs category code                 |
| hs\_chapter\_code  | *string* | 2 digit hs chapter code                  |
| hs\_chapter\_name  | *string* | Official hs chapter name                 |
| hs\_code           | *string* | 6 or 8 digit hs code                     |
| hs\_code\_id       | *string* | Unique reference for hs code.            |
| keywords           | *string* | List of keywords for describing hs code. |
| sub\_category      | *string* | Simplified description                   |


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.terminal.africa/tship/hs-codes-1.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.