The tap-amazon-mws extractor pulls data from Amazon MWS that can then be sent to a destination using a loader.
Alternate Implementations
- Adswerve (default)
-
dbt Labs
🥈
-
Ian McAllister
-
Matt Michie
-
Jack Park
🥈
Getting Started
Prerequisites
If you haven't already, follow the initial steps of the Getting Started guide:
Installation and configuration
-
Add the tap-amazon-mws extractor to your
project using
:meltano add -
Configure the tap-amazon-mws
settings using
:meltano config -
Test that extractor settings are valid using
:meltano config
meltano add extractor tap-amazon-mwsmeltano config tap-amazon-mws set --interactivemeltano config tap-amazon-mws testNext steps
Follow the remaining steps of the Getting Started guide:
If you run into any issues, learn how to get help.
Capabilities
The current capabilities for
tap-amazon-mws
may have been automatically set when originally added to the Hub. Please review the
capabilities when using this extractor. If you find they are out of date, please
consider updating them by making a pull request to the YAML file that defines the
capabilities for this extractor.
This plugin has the following capabilities:
- catalog
- discover
- state
You can
override these capabilities or specify additional ones
in your meltano.yml by adding the capabilities key.
Settings
The
tap-amazon-mws settings that are known to Meltano are documented below. To quickly
find the setting you're looking for, click on any setting name from the list:
You can also list these settings using
with the meltano configlist
subcommand:
meltano config tap-amazon-mws list
You can
override these settings or specify additional ones
in your meltano.yml by adding the settings key.
Please consider adding any settings you have defined locally to this definition on MeltanoHub by making a pull request to the YAML file that defines the settings for this plugin.
Access Key (access_key)
-
Environment variable:
TAP_AMAZON_MWS_ACCESS_KEY
Your Amazon MWS access key.
Configure this setting directly using the following Meltano command:
meltano config tap-amazon-mws set access_key [value]End Date (end_date)
-
Environment variable:
TAP_AMAZON_MWS_END_DATE
Date up to when historical data will be extracted.
Configure this setting directly using the following Meltano command:
meltano config tap-amazon-mws set end_date [value]Inventory Start Date (inventory_start_date)
-
Environment variable:
TAP_AMAZON_MWS_INVENTORY_START_DATE
The start date to use when syncing inventory data.
Configure this setting directly using the following Meltano command:
meltano config tap-amazon-mws set inventory_start_date [value]Marketplace IDs (marketplace_ids)
-
Environment variable:
TAP_AMAZON_MWS_MARKETPLACE_IDS
Your Amazon MWS marketplace IDs to sync data from.
Configure this setting directly using the following Meltano command:
meltano config tap-amazon-mws set marketplace_ids [value]Region (region)
-
Environment variable:
TAP_AMAZON_MWS_REGION
Your Amazon MWS region.
Configure this setting directly using the following Meltano command:
meltano config tap-amazon-mws set region [value]Secret Key (secret_key)
-
Environment variable:
TAP_AMAZON_MWS_SECRET_KEY
Your Amazon MWS secret key.
Configure this setting directly using the following Meltano command:
meltano config tap-amazon-mws set secret_key [value]Seller ID (seller_id)
-
Environment variable:
TAP_AMAZON_MWS_SELLER_ID
Your Amazon MWS seller ID.
Configure this setting directly using the following Meltano command:
meltano config tap-amazon-mws set seller_id [value]Start Date (start_date)
-
Environment variable:
TAP_AMAZON_MWS_START_DATE
Determines how much historical data will be extracted. Please be aware that the larger the time period and amount of data, the longer the initial extraction can be expected to take.
Configure this setting directly using the following Meltano command:
meltano config tap-amazon-mws set start_date [value]Something missing?
This page is generated from a YAML file that you can contribute changes to.
Edit it on GitHub!Looking for help?
#plugins-general
-1-c0c0c4){kind=icon}
