Amazon Selling Partner API Connector

SP-API is a suite of REST-based APIs that provides Amazon selling partners programmatic access to their Amazon Seller Central account. data.

4.8 on G2
Weld · Data Sources
Amazon Selling Partner APILive
orderSynced
returns_by_return_date_reportSynced
settlement_reportSynced
fba_returns_reportSyncing
sales_and_traffic_report_by_asinQueued
Lands insnowflakebigquerydatabricksAgent context over MCP
How it works

Set up in minutes.
No code, no maintenance.

Amazon Selling Partner API

Amazon Selling Partner API

Data source

Authenticating...
Ready to connect
Overview

Amazon Selling Partner API in your warehouse.
Ready for your agents.

SP-API is a suite of REST-based APIs that provides Amazon selling partners programmatic access to their Amazon Seller Central account. data. Weld's Amazon Selling Partner API connector is fully managed: it extracts data from Amazon Selling Partner API, loads it into your warehouse, and keeps it in sync. The data lands in a clean, documented schema with agent context attached, so analysts can query it with SQL or dbt, and agents can query it over the Weld MCP server without guessing at tables or joins.

AgentsQuery over MCPYour warehouse65 tables, with agent contextWeldExtract, load, keep in syncAmazon Selling Partner APISource
Agent context

Amazon Selling Partner API data schema.
The map your agents read.

Every table, field and relationship Weld syncs from Amazon Selling Partner API is served to agents as context over MCP, so they pick the right tables and join on the right keys.

tables
65
fields
987
relationships
3
Open the schema explorer
Open the full schema explorer
Weld MCP server

Ask your agent.
It already knows Amazon Selling Partner API.

Connect Claude, Cursor, ChatGPT or your own agent to Weld over MCP. It reads the Amazon Selling Partner API context, finds the tables it needs and queries your warehouse.

  • Agent contextAmazon Selling Partner API tables, fields and joins
  • QuerySQL against your warehouse
  • OperateCheck, rerun and refresh syncs
Claude CodeOpus 5
>

How many order rows do we have per order? Use our Amazon Selling Partner API data.

Reading the Amazon Selling Partner API context first, so the query uses the right tables and keys.

●weld·search_available_references
⎿raw.amazon_selling_api_oauth.order
raw.amazon_selling_api_oauth.order
+ 63 more Amazon Selling Partner API tables
●weld·get_reference_schema
⎿order · 26 columns
joins order on order_id
●weld·run_query
⎿select j.id, count(*) from {{raw.amazon_selling_api_oauth.order}} o
join {{raw.amazon_selling_api_oauth.order}} j on o.order_id = j.id
group by 1
submitted
●weld·get_query_status
⎿DONE
●weld·get_query_result
⎿rows returned
✓Answered from Amazon Selling Partner API data in your warehouse
>Ask about your Amazon Selling Partner API data
Weld Connect API

Set it up in code.
One REST API.

Use the Weld Connect REST API to create Amazon Selling Partner API connections, configure ELT syncs, and manage pipelines entirely through code. Built for embedding, automation, and CI/CD workflows.

POST/elt_syncs
▌
FAQ

Common questions.
About connectors.

Something not covered here? A data engineer can walk through your setup with you.

Talk to us

Put your Amazon Selling Partner API data to work.

Connect Amazon Selling Partner API, pick a warehouse, and your agents can query it today. Free for 14 days, no credit card.

Amazon Selling Partner APISource
WeldWeld
MCPAgents