Integrations
What SellZyme connects to.
SellZyme connects to Amazon through the official Advertising and Selling Partner APIs, and takes your product economics as an input — which is what lets it decide on contribution profit rather than ad metrics alone.
Connections
Where the data comes from
Prediction is only as good as its context. These are the inputs, and what each one is for.
Amazon Advertising API
CoreThe primary connection. Campaign structure, targeting, bids, budgets, placements, and search-term performance — read for prediction, written for execution.
Amazon Selling Partner API
CoreProduct, fee, and order context — the data that turns an ACOS number into a contribution-margin decision.
Product economics import
CoreYour cost of goods and margin, without which no tool can tell profitable spend from merely efficient spend.
Push notifications
CoreAlerts and approvals delivered to the mobile app, so urgent decisions don't wait for a desk.
Public API
PlannedProgrammatic access to predictions, recommendations, and action logs, for teams who want SellZyme's intelligence inside their own systems.
Slack & email digests
PlannedAccount health and approval queues delivered where your team already works.
Items marked planned are on the roadmap and not yet available. We list them so you can tell us if one of them is the thing you actually need.
FAQ
Integration questions
- How does SellZyme connect to Amazon?
- Through the official Amazon Advertising API and Selling Partner API, authorised via OAuth with least-privilege scopes. SellZyme never asks for your Seller Central password.
- Does SellZyme have a public API?
- Not yet. A public API for predictions, recommendations, and action logs is planned. If programmatic access is a requirement for you, tell us — it affects how we prioritise it.
- What data does SellZyme need to make predictions?
- Campaign and search-term performance history from the Advertising API, product and fee context from the Selling Partner API, and your cost of goods. The last one is what makes profit-based decisions possible rather than ACOS-based ones.

Need an integration we haven't built?
Tell us what your stack looks like. What we prioritise is shaped by what partners actually need.

