# Build the product. Not every marketplace integration.

MerchantSpring gives software teams and solution providers one governed data layer across 120+ marketplace, ecommerce, advertising, and retail-media channels. Bring sales, profit, advertising, and operational data into the product or workflow only you can build.

[Book a build walkthrough](https://merchantspring.io/solutions/builders#book-builder-walkthrough) [Read the technical docs](https://docs.merchantspring.io/)

## Keep the roadmap pointed at customer value.

Your product wins on insight, workflow, and user experience. None of that should disappear into marketplace authentication, account structures, and reporting differences.

### Your product owns

**The experience**  
The interface and interaction model your customers choose you for.

**The decision logic**  
Your models, recommendations, workflows, and proprietary point of view.

**The customer relationship**  
How the product is packaged, delivered, and improved over time.

### MerchantSpring handles

**Authorised connections**  
Marketplace, ecommerce, advertising, and retail-media access paths.

**Source-specific complexity**  
Different account structures, identifiers and reporting availability across channels.

**Structured delivery**  
Pre-aggregated reporting data exposed through approved API access.

**Build the differentiator. Buy the plumbing.** Use MerchantSpring as the data foundation, then invest engineering time in the product capability that is actually unique to your business.

## Meet customers where they already sell.

Start with authorised connections across global and regional channels, then bring the relevant reporting data into your own product experience. Most data layers stop at Amazon. Your customers do not.

.svg)

[See all supported channels](https://merchantspring.io/channels?hsLang=en)

## Use the data where it creates an advantage.

MerchantSpring is the reporting foundation. Your team decides where that foundation becomes a better product, a faster service, or a more useful internal system.

### Product teams

Add marketplace performance context to software your customers or internal teams already use, instead of starting with a connector roadmap.

Customer portals  
Decision tools  
Operational products

### Data teams

Move structured sales, product, financial, and advertising data into the environments where your organisation models and compares performance.

Data warehouses  
BI environments  
Internal analytics

### Solution providers

Deliver embedded analytics and automated reporting under your own brand, and spend specialist time on the advice and execution clients pay for.

Client reporting  
Portfolio analysis  
Repeatable delivery

## The same foundation supports AI workflows.

MerchantSpring MCP connects supported AI clients through the API Gateway, with data availability governed by the access on the developer profile.

Claude  
ChatGPT  
Cursor  
Codex  
Gemini CLI  
VS Code  
and more supported

[See the MerchantSpring MCP](https://merchantspring.io/feature/mcp?hsLang=en)

## A delivery path your team can plan.

API access is self-serve for MerchantSpring accounts. Generate a key from Settings, match the data fit against the docs, and make your first live call in under 5 minutes.

### Define the product

Clarify the customer, workflow and marketplace data the experience needs.

### Confirm coverage

Match required channels and datasets to the endpoints in the documentation.

### Get your API key

Generate a key MerchantSpring and authenticate.

### Build and monitor

Use the documentation and live examples, then monitor usage through the developer portal.

Endpoints, authentication, and examples live in the docs. [Read the technical docs](https://docs.merchantspring.io/)

## A foundation your buyers can review.

When your product runs on marketplace and commerce data, you need to be able to show where it comes from, what your access can touch, and how it's governed. MerchantSpring documents all three, so a reviewer doesn't have to take your word for it.

[Review security](https://merchantspring.io/security?hsLang=en) [Read the technical docs](https://docs.merchantspring.io/)

### Where data comes from

Connected marketplace and commerce data enters through authorised access paths.

### What the integration can use

Developer access is linked to a MerchantSpring account and subscribed to the approved APIs.

### Which reports apply

Compatibility is documented by channel type rather than presented as universal coverage.

### How usage is observed

API usage and limits are available through the developer portal.

## Questions before you build.

Who is this solution for?

Software companies, product teams, data teams, and solution providers that want marketplace reporting data inside an external product, internal system or repeatable client workflow.

What data can the API provide?

The full set of available endpoints is documented at [docs.merchantspring.io](https://docs.merchantspring.io/), including sales, products, financial events, refunds, and advertising performance.

Are the same reports available for every marketplace?

No. Report availability varies by channel type, plan, and add-on. Compatibility should be confirmed against the requirements of the proposed product.

Can the same foundation support AI workflows?

Yes. MerchantSpring MCP connects supported AI clients through the API Gateway, with data availability governed by the access on the associated developer profile.

Where should engineers go next?

Send implementation teams to [docs.merchantspring.io](https://docs.merchantspring.io/) for technical guidance and to the developer portal for credentials, testing, and usage.

## Bring us the product you want to build.

We will help you establish whether the required channels, datasets, and access model are a fit before your team commits to implementation.

Which marketplaces and accounts need to connect?

Which reporting datasets does the product require?

Where will the data appear in your customer or internal workflow?