# Address Management Guide

Easyparser allows you to define custom delivery addresses to simulate location-based results in your API responses. These addresses act as Amazon delivery locations and help tailor the data returned based on availability, pricing, and shipping options for specific regions.

You can manage these addresses directly in the [Easyparser Web App](https://app.easyparser.com/) through the [Address Management Page](https://app.easyparser.com/addresses). Depending on your subscription plan, you can add one or more addresses, each identified by a unique address\_id, which you can include in your API requests.

{% stepper %}
{% step %}

### Add a New Address

If you haven’t added any addresses yet, you’ll see an informative prompt on the page along with an “Add Address” button at the bottom.

Once you click the “Add Address” button, a modal modal titled “Add a New Address” will appear.

{% hint style="info" %}
Please note that the number of addresses a member can add depends on their subscription plan. You can view available plans [here](https://easyparser.com/pricing).
{% endhint %}

<figure><img src="/files/t2ld9IrcsbCnjIKzkhdS" alt=""><figcaption></figcaption></figure>

{% endstep %}

{% step %}

#### &#x20;**Add a Title**

**Add a title** for easy identification (optional).
{% endstep %}

{% step %}

#### Choose **Amazon Domain**&#x20;

Choose the **Amazon platform and domain** (e.g., `amazon.com`, `amazon.co.uk`, etc.).
{% endstep %}

{% step %}

#### **Enter the ZIP Code**

Enter the **ZIP code** (e.g., `60302`) or other required location details.
{% endstep %}

{% step %}
**Select ZIP/Postal code Or By Country/City**

Select whether you want to add by **ZIP/postal code** or by **country/city** (depending on the domain).
{% endstep %}

{% step %}
**Deliver To**

You need to add the address found in the 'Deliver to' field on amazon.com to this field.

<figure><img src="/files/ZyUrzBlFM6ppt08c8eg1" alt=""><figcaption></figcaption></figure>
{% endstep %}

{% step %}

#### Choose Language

Choose the **preferred language** (e.g., `en_US`, `es_US`).
{% endstep %}

{% step %}

#### **Add Zipcode**

Finally, click **“Add Zipcode”** to submit.

<figure><img src="/files/Gb0jKOgbsWFCKbcIv8ue" alt=""><figcaption></figcaption></figure>
{% endstep %}

{% step %}

### :movie\_camera: View and Manage Your Addresses

Once you’ve submitted a new address, it will appear in your address list with a unique **ID** and relevant details such as domain, type, and value.

&#x20;🔄Status Updates

* Initially, the **Status** column might show `"Preparing"` this means the address is being validated.
* Within a short time (as long as the information is valid), the status will change to **"Active"**.
* Only **Active** addresses can be used in API requests.

<figure><img src="/files/CXYGNMOXtD6JCFxMZmym" alt=""><figcaption></figcaption></figure>
{% endstep %}

{% step %}

### Status Actions

From the "Actions" section located at the far right of the address list, you can either set an address to **Inactive** status or delete it completely.

<figure><img src="/files/b7yFJ4UJS3phOPfU2wvS" alt=""><figcaption></figcaption></figure>
{% endstep %}

{% step %}

### Implementing Address ID in Operations

Once your addresses are defined, you can use their unique IDs to customize your data extraction. This ensures that fields like price, stock, and images are fetched specifically for your target location.

* #### Identifying and Selecting Address ID

  In the Easyparser dashboard, you can select your predefined addresses directly from the interface.

  * Navigate to the Address ID (Zipcode) dropdown.
  * Selecting a Zipcode (e.g., `20318`) automatically maps to its internal ID (e.g., `722`).

<figure><img src="/files/nZYc9yaL8iYl5NRF5K1z" alt=""><figcaption></figcaption></figure>

* #### Real-Time API Requests

  For individual or real-time requests, the `address_id` must be added as a query parameter. This allows you to switch locations dynamically without changing your global settings.\
  \
  Example Request cURL:

{% code overflow="wrap" %}

```javascript
curl --location 'https://realtime.easyparser.com/v1/request?
  api_key=YOUR_API_KEY&
  platform=AMZ&
  operation=DETAIL&
  address_id=722&
  domain=.com&
  language=en_US&
  asin=B0BP7JJWHC&
  a_plus_content=false'
```

{% endcode %}

* #### Usage in Bulk Operations

  When performing high-volume tasks, the `address_id` should be placed at the Root Level of your JSON object. This allows you to process thousands of items for a specific region in a single \
  \
  Bulk Integration Example (cURL):

{% code overflow="wrap" %}

```javascript
curl --location 'https://bulk.easyparser.com/v1/bulk' \
--header 'api-key: YOUR_API_KEY' \
--header 'Content-Type: application/json' \
--data '[    
    {
        "platform": "AMZ",
        "operation": "DETAIL",
        "domain": ".com",
        "address_id" : 722,
        "payload": {
            "asins": [
                       "B0BP7JJWHC"
            ]
        },
        "callback_url": "https://example.com/webhook"
    }
]'
```

{% endcode %}
{% endstep %}
{% endstepper %}


---

# Agent Instructions: 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:

```
GET https://easyparser.gitbook.io/easyparser-documentation/amazon/address-management-guide.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.