# Common Required Request Fields

<table data-full-width="false"><thead><tr><th width="186">Field</th><th width="207">Type</th><th width="275">Description</th></tr></thead><tbody><tr><td><code>api_key</code></td><td>string</td><td>Your API key for authentication</td></tr><tr><td><code>platform</code></td><td>string</td><td>Target platform (e.g. <code>Amazon</code>)</td></tr><tr><td><code>domain</code></td><td>string</td><td>Amazon marketplace domain (e.g. <code>.com</code>, <code>.co.uk</code>, <code>.de</code>, etc.)</td></tr><tr><td><code>operation</code></td><td>string</td><td>Name of the operation to perform (e.g. <code>Detail</code>, <code>Offer</code>, <code>Search</code>)</td></tr><tr><td><code>asin</code> / <code>url</code> / <code>keyword</code>  / <code>seller_id</code>  </td><td>string</td><td>Product identifier  ASIN, URL, KEYWORD or SELLER_ID. At least one required in most operations</td></tr></tbody></table>


---

# 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/common-required-request-fields.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.