A previous release had provenance metadata, but this release does not. View details.
Amazon Selling Partner Python Library
The Amazon Selling Partner Python library provides convenient access to the Amazon Selling Partner API from applications written in the Python language. It includes a pre-defined set of classes for API resources and it is compatible with the latest versions of the Amazon Selling Partner API.
- Discussions: https://github.com/dbritto-dev/amzn-selling-partner-python/discussions
- Bug reports: https://github.com/dbritto-dev/amzn-selling-partner-python/issues
- Source code: https://github.com/dbritto-dev/amzn-selling-partner-python
Documentation
- Tutorial: https://developer-docs.amazon.com/sp-api/docs/tutorial-create-a-private-selling-partner-api-application
- AWS Lambda Demo: https://github.com/aws-quickstart/quickstart-amazon-selling-partner-api/blob/main/functions/source/ExampleLambda/lambda_function.py
- Get AWS secret keys: https://docs.aws.amazon.com/powershell/latest/userguide/pstools-appendix-sign-up.html
- Reports Tutorial: https://developer-docs.amazon.com/sp-api/docs/reports-api-v2021-06-30-tutorial-request-a-report
- Report Types for Vendor: https://developer-docs.amazon.com/sp-api/docs/report-type-values-analytics#vendor-retail-analytics-reports
- Market Place Ids: https://developer-docs.amazon.com/sp-api/docs/marketplace-ids
- API Endpoints and Regions: https://developer-docs.amazon.com/sp-api/docs/sp-api-endpoints
- API Endpoints and Regions (Sandbox): https://developer-docs.amazon.com/sp-api/docs/the-selling-partner-api-sandbox
Installation
Install with uv
uv sync
Install the development tools with:
uv sync --extra dev
Install from a GitHub private repo
TOKEN="<token>" pip install git+https://dbritto-dev:$TOKEN@github.com/dbritto-dev/amzn-selling-partner-python.git
Install from source
uv pip install .
Requirements
- Python 3.10 or later (PyPy supported)
Usage
This library needs to be configure with your account's secret keys: Selling Partner Keys and AWS Keys.
Set up the next environment variables. We can use dotenv to load them locally.
# Fetch "client id" and "client secret" from your application in Seller Central
# by clicking on "View" in front of your application ID.
SELLING_PARTNER_APP_CLIENT_ID=
SELLING_PARTNER_APP_CLIENT_SECRET=
# In order to call an API for a seller, you will need to paste the
# refresh_token for that particular seller below. You can get refresh token for
# a seller using OAuth flow. Otherwise, you can self-authorize your application
# by clicking on "Authorize" from the dropdown menu in front of your
# application ID in seller central. Once you click on "Generate Refresh Token",
# you would be able to receive a refresh token and paste it below.
SELLING_PARTNER_APP_REFRESH_TOKEN=
# Pull out "access key ID" and "secret access key" from IAM console by cliking on
# "Users" navigation menu option and opening "Security Credentials" tab.
AWS_ACCESS_KEY_ID=
AWS_SECRET_ACCESS_KEY=
# This role is necessary to create temporary credentials to the call Selling Partner API, to read
# more about which policies and resources are needed for this role, here's the link (click on ->
# `Select to expand the manual steps to create and configure IAM policies.` to read more about that)
# https://developer-docs.amazon.com/sp-api/docs/tutorial-create-a-private-selling-partner-api-application#step-3-create-and-configure-iam-resources
# The role session name is just the label that we set up for those temporary credentials
AWS_SELLING_PARTNER_ROLE=
AWS_SELLING_PARTNER_ROLE_SESSION_NAME=
import amzn_selling_partner.vendor as sp
sp_vendor_orders_client = sp.vendor.orders.Client()
purchase_orders = sp_vendor_orders_client.get_purchase_orders()
print(purchase_orders)
purchase_order = sp_vendor_orders_client.get_purchase_order("<purchase-order-number>")
print(purchase_order)
Handling exceptions
Unsuccessful requests raise exceptions. The errors should handled as Requests library exceptions.
To read more about that: https://requests.readthedocs.io/en/latest/user/quickstart/#errors-and-exceptions
Per-client configuration
Configure individual clients with keyword arguments. For instance, you can make a request with a specific selling partner region or use sandbox.
import amzn_selling_partner.vendor as sp
na_sp_vendor_orders_client = sp.vendor.orders.Client(
selling_partner_region=client.SellingPartnerRegion.NORTH_AMERICA
)
eu_sp_vendor_orders_client = sp.vendor.orders.Client(
selling_partner_region=client.SellingPartnerRegion.EUROPE
)
fe_sp_vendor_orders_client = sp.vendor.orders.Client(
selling_partner_region=client.SellingPartnerRegion.FAR_EAST
)
Enable Sandbox
import amzn_selling_partner.vendor as sp
sp_vendor_orders_client = sp.vendor.orders.Client(sandbox=True)
Note: some endpoints are not available on sandbox. To read more about that: https://developer-docs.amazon.com/sp-api/docs/the-selling-partner-api-sandbox
Development
Install from source
uv sync --extra dev
Type checking
uv run ty check src/amzn_selling_partner
Lint and format
uv run nox -s lint
Test
uv run nox -s test
Security checks
uv run nox -s security_test
CI
Lint, tests, type checking, and security checks run automatically on every push and pull request via GitHub Actions, across Python 3.10 through 3.13.
Metadata
Release files for amzn-selling-partner 0.1.10
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Loss of provenance
These files do not have provenance metadata, despite files in a prior release including this data.
We recommend further investigation before installing these files. View details.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| amzn_selling_partner-0.1.10.tar.gz | 12.1 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| amzn_selling_partner-0.1.10-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 28.4 kB
Release files / amzn_selling_partner-0.1.10.tar.gz
Loss of provenance
This file belongs to a release without provenance metadata, despite a prior release including this data.
We recommend further investigation before installing this file. View details.
| Download URL | amzn_selling_partner-0.1.10.tar.gz |
|---|---|
| Size | 12.1 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
e5a086f482225a28d4cbe6ee3573ac7abe13b90354b4c7607befa0921140acb4
|
|
BLAKE2b-256 checksum How to use checksums |
2daf4cfdc10ac5cbef5072cdbc2e76a6fa37d94cfe4c674d733a294383e4b3c8
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
uv/0.12.13 {"installer":{"name":"uv","version":"0.12.13","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"Ubuntu","version":"24.04","id":"noble","libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":true}
|
Release files / amzn_selling_partner-0.1.10-py3-none-any.whl
Loss of provenance
This file belongs to a release without provenance metadata, despite a prior release including this data.
We recommend further investigation before installing this file. View details.
| Download URL | amzn_selling_partner-0.1.10-py3-none-any.whl |
|---|---|
| Size | 16.3 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
e11f17cae0430d8ed1848e7f28710f5f9bafe8fc4fda3e13bd0158d48b81ae17
|
|
BLAKE2b-256 checksum How to use checksums |
89fb5aaa8a3184a41cba4840e119dff39d1f5f651d897a86d09a12cf51d98cfb
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
uv/0.12.13 {"installer":{"name":"uv","version":"0.12.13","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"Ubuntu","version":"24.04","id":"noble","libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":true}
|
Security for amzn-selling-partner 0.1.10
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
Loss of provenance
A previous release of these files had provenance metadata, but this release does not.
While this could reflect a routine change by the project maintainers, it may also indicate that the release files have been compromised.
Release comparison
- Removed 0.1.7 2 files With provenance
- Added 0.1.10 2 files Without provenance
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.