Start with use cases
Define whether your team needs alerts, BI datasets, OAuth connectors, partner access or automation before selecting scope.
Programmatic KPIsCommercial scope guide
Plans and API scope that match your marketplace maturity.
Choose the API, export, connector and automation surface that fits your current channels, team responsibilities and rollout risk.
API access
Export cadence
Connector scope
Scope decisions
Match data volume
Use exports for warehouse and finance workloads, and REST API access for current-state checks or internal tools.
Warehouse datasetsPhase automation
Roll out read access, reviewed recommendations and automated actions in stages so teams can build trust.
Pricing overview
Buying and rollout
The right scope depends on workflow risk, not only request volume.
A small team with high-risk automation may need stronger governance than a larger team using read-only exports. Scope should follow the operating model.
Separate access from outcomes
API access is useful when it supports a business workflow. Start from the reporting, alerting or automation outcome, then choose endpoints and exports.
Plan around stakeholder ownership
Finance, marketplace operations, agencies and engineering teams often need different data shapes. Scope should reflect who owns each workflow.
Leave room for maturity
Teams usually start with visibility, then add recommendations, and only then automate high-impact commercial actions.
Recommended workflow
How to move from idea to production workflow
-
01
Inventory marketplaces, webshops, ad channels and internal systems.
-
02
Split requirements into REST, export, OAuth and automation needs.
-
03
Define rollout phases with owners, success metrics and review moments.
-
04
Choose plan scope based on the workflows that must be reliable first.
Build the API workflow with the right scope from day one.
Bring your channels, reporting needs and automation goals. We will map the safest route across REST, exports, OAuth and governance.