> 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/pricing-advisor-api/resources/first-successful-requests/storefront-pricing-engineer.md).

# Storefront Pricing Engineer

Retrieve the latest **standard pricing advice** for one tenant and one shopper country using:

```http
GET /api/4.0/StandardAdvice/{tenantCode}/{countryIso}
```

This endpoint is retrieves the latest available pricing advice for a country. The response is `PricingAdviceResponse`, which includes `fxRates`, `categories`, and `merchandisePricingModel`.

### Why this is the best first request

It gives the latest market-specific advice for one country without requiring historical IDs or portfolio-wide queries. It is also the best way to prove that auth, tenant scoping, and country targeting are all working.

### First request

{% code title="BASE URL" expandable="true" %}

```hurl
https://pricing-advisor-api.sandbox.eshopworld.com
```

{% endcode %}

| Name                                                        | Description                                                                                  |
| ----------------------------------------------------------- | -------------------------------------------------------------------------------------------- |
| `tenantCode` <mark style="color:$danger;">`required`</mark> | Six-letter code that identifies the tenant.                                                  |
| `countryIso`<mark style="color:$danger;">`required`</mark>  | ISO 3166 code of the delivery country that will be impacted by the product price adjustment. |

{% tabs %}
{% tab title="Try it" %}
{% @code-walkthrough/try-it specLoaded="" specEps="" method="GET" path="/api/4.0/StandardAdvice/{tenantCode}/{countryIso}" baseUrl="<https://api.example.com>" title="GET pricing advice for a country." defaults="{"path":{"tenantCode":"","countryIso":""},"query":{},"headers":{"Content-Type":"application/json"}}" mode="closed" %}
{% endtab %}
{% endtabs %}

```json
curl -X GET "https://<your-host>/api/4.0/StandardAdvice/TEN123/US" \
  -H "Authorization: Bearer <JWT>" \
  -H "Accept: application/json"
```

### What success looks like

A successful first result is <mark style="color:$success;">`200 OK`</mark> with a `PricingAdviceResponse`. At minimum, you should expect top-level fields such as:

* `id`
* `version`
* `countryIso`
* `lastUpdated`
* `tenantIdentifier`
* `fxRates`
* `categories`
* `merchandisePricingModel`

### What to do next

After this first success, the next useful step is to inspect `categories[].estimatedTax`, `estimatedFee`, `estimatedDuty`, and `retailerAdjustment`, plus `merchandisePricingModel.applicableRates`, because those are the fields most directly tied to pricing logic.


---

# 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/pricing-advisor-api/resources/first-successful-requests/storefront-pricing-engineer.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.