> For the complete documentation index, see [llms.txt](https://developer.esw.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://developer.esw.com/customs-catalog-api/resources/first-successful-requests/duty-and-tax-rules-manager.md).

# Duty and Tax Rules Manager

This persona maps to the `DutyRule` tag.

The `GET` supports filters like `RuleType`, `Country`, `TenantCode`, and `HsCode`.

### Best first request

Use `GET /api/v2/DutyRule?TenantCode=TENANT_01`. It is the best way to prove you can query existing rules before attempting an upsert.

#### Query Parameters

| Parameter    | Type     | Description                    |
| ------------ | -------- | ------------------------------ |
| `RuleType`   | `string` | Filter by rule type.           |
| `Country`    | `string` | Filter by destination country. |
| `TenantCode` | `string` | Filter by tenant code.         |
| `HsCode`     | `string` | Filter by HS code.             |

```json
curl -X GET "https://logistics-customscatalog-api.sandbox.eshopworld.com/api/v2/DutyRule?TenantCode=TENANT_01" \
  -H "Authorization: Bearer <JWT>"
```

### What success looks like

A <mark style="color:$success;">`200 OK`</mark> returns an array of `DutyRuleSearchResponse` objects. The model includes `ruleType`, `rateType`, `additionalDuty`, and `id`. The contract also allows <mark style="color:$danger;">`404 Not Found`</mark>, so for a guaranteed happy-path sandbox demo you should use a tenant known to have seeded rules.

{% tabs %}
{% tab title="Try it" %}
{% @code-walkthrough/try-it specLoaded="" specEps="" method="GET" path="/api/v2/DutyRule" baseUrl="<https://logistics-customscatalog-api.sandbox.eshopworld.com/>" title="Returns Duty Rules" defaults="{"path":{},"query":{"RuleType":"","Country":"","TenantCode":"","HsCode":""},"headers":{"Content-Type":"application/json"}}" mode="closed" %}
{% endtab %}
{% endtabs %}


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://developer.esw.com/customs-catalog-api/resources/first-successful-requests/duty-and-tax-rules-manager.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.