# Response The response for the Product Lookup operation provides a comprehensive mapping between your submitted identifier and the resulting Amazon listings. Since a single universal identifier (like a UPC or EAN) can occasionally be associated with multiple ASINs on Amazon, the response is structured as a list to ensure no data is missed. The JSON response is organized to separate request telemetry from the core product data. By nesting the extracted information within the `result` object, the API maintains a clean logical flow for developers. API Response Structure Overview The JSON response is organized into four primary sections: * **`request_info`**: Contains the status of the API call, a unique request ID, and detailed credit consumption information to help you monitor your account balance in real-time. * **`request_parameters`**: Echoes back the parameters you sent, such as the identifier and identifier type, to confirm the exact query processed by the engine. * **`request_metadata`**: Includes precise timestamps regarding when the request was created and processed, providing visibility into system performance. * **`result`**: Contains the core payload, including the search results, multi-identifier arrays, and product-specific attributes. These fields provide essential information about the transaction status, the input parameters, and the overall processing timing, ensuring a predictable and easy-to-parse integration. ## **1. Top-Level Meta Fields (Outside of `result`)** Contains general metadata about the request, such as status, credits, parameters, and processing information. ### `request_info`(object) Contains meta-information about the API request itself, including its status, error details, and credit usage. | Field | Type | Description | Example | | --------------------------- | ------- | -------------------------------------------------------------------------------------- | -------------------------- | | id | String | The unique transaction ID assigned to the specific request. | `9e091b92-212d...` | | success | Boolean | Indicates whether the operation was successfully executed. | `true` | | status\_code | Integer | The standard HTTP status code returned by the server. | `200` | | error\_details | Array | Contains specific error messages if the request fails (empty on success). | `[]` | | credits\_used | Integer | The total number of credits consumed by your account during the current billing cycle. | `1` | | credit\_used\_this\_request | Integer | The number of credits deducted specifically for this individual operation. | `1` | | credits\_remaining | Integer | The total amount of credits remaining in your account after this request. | `99` | | credits\_reset\_at | String | The ISO 8601 timestamp indicating when your credit balance will next reset. | `2026-04-09T07:41:48.000Z` | ### `request_parameters` (object) The `request_parameters` object serves as an "echo" of the input values you provided in your API request. This section is vital for logging and debugging, as it allows you to verify that the Easyparser engine received and processed the correct identifier and operation type. | identifier | String | The specific numerical or alphanumeric product code you submitted for the lookup. | `724382975021` | | ---------------- | ------ | --------------------------------------------------------------------------------- | ---------------- | | identifier\_type | String | The classification of the provided code (e.g., UPC, EAN, ASIN, GTIN). | `UPC` | | type | String | The specific operation name executed by the API. | `PRODUCT_LOOKUP` | ### `request_metadata` (object) The `request_metadata` object provides high-level performance metrics for your API call. These timestamps and duration values allow you to monitor the efficiency of the data extraction process and audit the timing of your requests. | created\_at | String | The UTC timestamp indicating when the request was first received by our system. | `2026-03-16T13:09:27.218Z` | | ------------------ | ------ | --------------------------------------------------------------------------------------------------- | -------------------------- | | processed\_at | String | The UTC timestamp indicating when the data extraction was completed and the response was generated. | `2026-03-16T13:09:31.746Z` | | total\_time\_taken | Float | The total duration in seconds required to process the request from start to finish. | `4.528` | ## 2. Core Response Payload – `result` Section The `result` object contains the heart of the Product Lookup response. This section houses the marketplace-specific data and the collection of products that match your queried identifier. It is architected to handle both unique 1:1 matches and complex 1:N relationships where a single identifier points to multiple Amazon listings. ### `result` (object) | Field | Type | Description | Example | | -------------- | ------ | ----------------------------------------------------------------------------------------------- | ---------------------------- | | country\_code | String | The ISO alpha-2 code representing the specific Amazon marketplace where the data was retrieved. | `US` | | search\_result | Object | A dedicated container for the lookup results, including the total count and the product array. | See detailed breakdown below | ### `search_result` **(object)** This object provides a summary of the lookup findings, allowing you to quickly determine how many products were identified before iterating through the data. | total\_product\_count | Integer | The total number of unique Amazon listings that match the provided identifier. | `2` | | --------------------- | ------- | --------------------------------------------------------------------------------- | ---------------------------- | | products | Array | An array of detailed product objects containing metadata and identifier mappings. | See detailed breakdown below | ### **`products[]` (object) Example Attributes** Each entry within the `products` array represents an individual Amazon listing. This object provides a rich set of data, from commercial identifiers to visual assets and manufacturer details.
FieldTypeDescriptionExample
asinStringThe unique Amazon Standard Identification Number for the listing.B000024D4S
titleStringThe full, official product title as it appears on Amazon.Wish You Were Here
brandStringThe brand name associated with the product listing.Parlophone
manufacturerStringThe entity responsible for the production of the item.Capitol
model_numberStringThe manufacturer's specific model or part number.CDEMD1062
linkStringThe direct canonical URL to the product's detail page.https://www.amazon.com/dp/...
image_urlString

[Scheduled for Removal]

A direct string URL to the primary high-resolution product image.

https://m.media-amazon.com/...
thumb_string_urlString

[Scheduled for Removal]

A direct string URL to an optimized thumbnail version of the image.

https://m.media-amazon.com/...
main_imageObjectA structured object containing the primary image ID and link.{ "id": "...", "link": "..." }
thumb_imageObjectA structured object containing the thumbnail image ID and link.{ "id": "...", "link": "..." }
identifiersArrayA collection of global codes (UPC, EAN, GTIN, etc.) linked to this ASIN.See detailed breakdown below
### **`product.identifiers`** (Array) This nested array is a key component of the Product Lookup operation. It lists all standard identifiers registered in the Amazon catalog for that specific listing. This allows developers to map an ASIN back to its global retail counterparts. | type | String | The classification of the identifier (e.g., upc, ean, gtin, isbn). | `upc` | | ----- | ------ | ------------------------------------------------------------------ | -------------- | | value | String | The numerical or alphanumeric value of the specific product code. | `724382975021` | #### Multi-Product Matching Logic In the Amazon ecosystem, it is possible for a single global identifier (such as an EAN or UPC) to be associated with multiple ASINs. This typically occurs with bundle offers, multi-packs, or legacy listings. The Product Lookup operation is designed to handle these 1:N (One-to-Many) relationships by returning every matching listing within the `products` array. * If `total_product_count` is 1, it is a unique match. * If `total_product_count` is greater than 1, your application should iterate through the array to identify the most relevant listing for your use case. ## Sample Output Below is a complete, live-environment example of a Product Lookup response using a UPC identifier. This sample demonstrates a scenario where a single code matches two distinct Amazon listings. {% code overflow="wrap" %} ```json { "request_info": { "id": "7cdbc505-5642-4882-9e2e-6dd99dfbd8af", "success": true, "status_code": 200, "error_details": [], "credits_used": 1, "credit_used_this_request": 1, "credits_remaining": 99, "credits_reset_at": "2026-04-09T07:41:48.000Z" }, "request_parameters": { "identifier": "724382975021", "identifier_type": "UPC", "type": "PRODUCT_LOOKUP" }, "request_metadata": { "created_at": "2026-03-16T22:16:42.169Z", "processed_at": "2026-03-16T22:16:46.401Z", "total_time_taken": 4.232 }, "result": { "search_result": { "products": [ { "asin": "B000024D4S", "brand": "Parlophone", "identifiers": [ { "type": "upc", "value": "724382975021" }, { "type": "ean", "value": "0724382975021" }, { "type": "gtin", "value": "00724382975021" } ], /* Scheduled for Removal - Use main_image instead */ "image_url": "https://m.media-amazon.com/images/I/71m0ofUWYXL.jpg", "link": "https://www.amazon.com/dp/B000024D4S", "main_image": { "id": "71m0ofUWYXL", "link": "https://m.media-amazon.com/images/I/71m0ofUWYXL.jpg" }, "manufacturer": "Capitol", "model_number": "CDEMD1062", "thumb_image": { "id": "510mQlM8AVL", "link": "https://m.media-amazon.com/images/I/510mQlM8AVL._SL75_.jpg" }, /* Scheduled for Removal - Use thumb_image instead */ "thumb_string_url": "https://m.media-amazon.com/images/I/510mQlM8AVL._SL75_.jpg", "title": "Wish You Were Here" }, { "asin": "B00745CZ3Y", "brand": "EMI", "identifiers": [ { "type": "upc", "value": "724382975021" }, { "type": "ean", "value": "0724382975021" } ], /* Scheduled for Removal - Use main_image instead */ "image_url": "https://m.media-amazon.com/images/I/61h7Q2eFq0L.jpg", "link": "https://www.amazon.com/dp/B00745CZ3Y", "main_image": { "id": "61h7Q2eFq0L", "link": "https://m.media-amazon.com/images/I/61h7Q2eFq0L.jpg" }, "manufacturer": "EMI", "thumb_image": { "id": "413RSoCQ+ZL", "link": "https://m.media-amazon.com/images/I/413RSoCQ+ZL._SL75_.jpg" }, /* Scheduled for Removal - Use thumb_image instead */ "thumb_string_url": "https://m.media-amazon.com/images/I/413RSoCQ+ZL._SL75_.jpg", "title": "Wish You Were Here" } ], "total_product_count": 2 }, "country_code": "US" } } ``` {% endcode %} --- # 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/real-time-integration/product-lookup/response.md?ask= ``` 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.