> For the complete documentation index, see [llms.txt](https://docs.pandium.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.pandium.com/connectors/connectors-101/amazon.md).
# Amazon
Set up the Amazon OAuth2 connector in Pandium using your app ID, client credentials, and seller marketplace region so tenants can authenticate and sync eCommerce data securely.
## **Connector Overview**
Amazon is an eCommerce and cloud computing giant that provides a wide range of services including online retail, cloud storage, and artificial intelligence tools.
## **Authentication Type**
OAuth2
## **Webhook Supported**
No
## **Secrets**
* PAN\_SEC\_AMAZON\_APP\_ID
* PAN\_SEC\_AMAZON\_CLIENT\_IDENTIFIER
* PAN\_SEC\_AMAZON\_CLIENT\_SECRET
* PAN\_SEC\_AMAZON\_APPLICATION\_IN\_DRAFT\_
## **API Client Supported**
No
## **Requirements for Provisioning**
In order to provision your connector, the following Amazon information must be gathered:
* App ID
* Client identifier
* Client secret
* Application In Draft?
## **How to Connect Your Integration**
Upon successfully creating a tenant, you will use the following information to connect to Amazon:
* Amazon Seller Marketplace Region
## **API Resources**
For more information on how to utilize the Amazon API, feel free to reference the following [documentation](https://aws.amazon.com/api-gateway/).
---
# 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 following URL with the `ask` and `goal` query parameters:
```
GET https://docs.pandium.com/connectors/connectors-101/amazon.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `build a script that syncs our docs to a CMS` lets GitBook tailor the answer to that use case.
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.
