How to Use Amazon's SP-API Without Being a Developer

What Is the SP-API?

The Selling Partner API (SP-API) is Amazon's official data interface that powers every third-party seller tool on the market. It's a set of REST-based APIs that lets authorised applications access your Amazon seller data: orders, inventory, advertising, catalogue, finances, and more.

Every tool you've heard of — Helium 10, Jungle Scout, Sellerboard, Jarvio — is built on this API. They all access the same underlying data from Amazon's servers. The difference between tools isn't what data they can get (they all get the same data), it's what they do with it and how they present it to you.

Understanding the SP-API helps you understand what's possible with Amazon seller tools. If a tool claims to offer a feature, you can ask: "Does the API actually support this?" Knowing the API's capabilities and limitations makes you a more informed buyer of seller tools and a better evaluator of tool claims.

The MWS to SP-API Migration

Before SP-API, Amazon used the Marketplace Web Service (MWS), a SOAP-based API that was powerful but dated. Amazon began deprecating MWS in 2020 and fully retired it by 2024. The migration was significant because SP-API introduced several important changes.

Better security. SP-API uses OAuth 2.0 authentication with rotating access tokens, replacing MWS's static credential model. This means tighter access control and reduced risk of credential theft.

Granular permissions. Instead of all-or-nothing access, SP-API lets sellers grant tools access to specific data types. You can authorise a PPC tool to access advertising data without giving it access to your financial data.

More data. SP-API provides access to data that wasn't available through MWS, including Brand Analytics, Search Query Performance data, and more granular inventory health metrics.

Better rate limits. SP-API handles request throttling more gracefully, allowing higher throughput for authorised applications that need to process large data volumes.

What Data It Provides

The SP-API is organised into distinct API sections, each covering a different operational area. Here's what each section provides:

• Orders API: Every order, refund, return, and cancellation with full buyer details (within Amazon's privacy constraints), shipping information, and financial breakdown
• Inventory API: FBA stock levels by fulfilment centre, inbound shipment status, aged inventory data, stranded inventory alerts, and reserved quantity details
• Catalog API: Product attributes, listing content, category data, variation relationships, and product identifier mapping (ASIN, UPC, EAN)
• Finances API: Settlement reports, fee breakdowns, reimbursement records, payment details, and financial event groups
• Reports API: Business reports, search term reports, Brand Analytics, inventory health reports, and dozens of specialised report types
• Feeds API: Push data to Amazon — listing updates, price changes, inventory quantities, and flat file uploads
• Notifications API: Real-time notifications for order events, listing changes, and inventory updates

Key API Endpoints Explained

Not all API endpoints are created equal. Some provide data that's genuinely transformative for your business, while others are primarily useful for operational infrastructure. Here's what matters most to sellers.

GET_SALES_AND_TRAFFIC_REPORT. This is the SP-API equivalent of the Business Reports you see in Seller Central. It provides sessions, page views, Buy Box percentage, units ordered, and revenue by ASIN and by date. This is the foundation of most analytics tools.

GET_MERCHANT_LISTINGS_ALL_DATA. A complete export of your active catalogue with all attributes: titles, prices, quantities, identifiers, fulfilment channels, and status. Essential for catalogue management and duplicate detection.

GET_FBA_MYI_UNSUPPRESSED_INVENTORY_DATA. Your current FBA inventory snapshot including available quantity, reserved quantity, inbound quantity, and total quantity by SKU and fulfilment centre. This powers inventory management and restock alert features.

GET_BRAND_ANALYTICS_SEARCH_TERMS. Available only to brand-registered sellers, this endpoint provides search frequency rank, click share, and conversion share for your brand's search terms. It's one of the most valuable data sources Amazon offers.

Advertising API — Campaign Reports. Technically a separate API, but most tools connect to both. Provides campaign performance, keyword data, search term reports, and bid information for Sponsored Products, Brands, and Display.

Why Sellers Should Care

Understanding the SP-API matters for three practical reasons that directly affect your bottom line.

Data portability. Your Amazon data isn't locked into any one tool. Any tool that connects to the SP-API can access the same underlying data. If you switch from Tool A to Tool B, Tool B gets the same data quality. This means your choice of tool should be based on what it does with the data, not what data it can access.

Feature validation. When a tool claims a unique feature, you can evaluate whether it's genuinely unique or just a different presentation of standard SP-API data. A tool that claims "proprietary sales data" is almost certainly using the same GET_SALES_AND_TRAFFIC_REPORT that every other tool uses.

Automation ceiling. The API defines what can be automated. PPC management can be fully automated because the Advertising API supports campaign creation, bid adjustment, and keyword management. Product photography can't be automated through the API because there's no endpoint for it. Knowing these boundaries helps you set realistic expectations for any tool.

Why Building on It Is Hard

The SP-API is powerful but notoriously complex to work with. Here's what makes it difficult, even for experienced engineers.

Authentication complexity. SP-API uses OAuth 2.0 with Login with Amazon (LWA) and STS role-based access. You need to manage refresh tokens, access tokens, and assumed roles. Tokens expire, and handling token refresh gracefully under high request volumes is non-trivial.

Rate limiting. Each endpoint has its own rate limits, measured in requests per second and burst limits. Hit a rate limit and you get throttled. Your application needs to implement exponential backoff, request queuing, and rate-limit tracking across all endpoints simultaneously.

Data format inconsistency. Different endpoints return data in different formats. Some use JSON, others return compressed tab-delimited files that need to be requested, polled for completion, downloaded, decompressed, and parsed. Report endpoints are particularly complex — you request a report, poll until it's ready, download the document, and then process it.

Ongoing maintenance. Amazon updates the SP-API regularly, sometimes deprecating endpoints with limited notice. Your engineering team needs to monitor changelog notifications, test against sandbox environments, and update your integration before deprecated endpoints stop working.

Multi-marketplace complexity. If you sell on multiple Amazon marketplaces, each marketplace has its own endpoint URL, authentication flow, and regional rate limits. A US-only integration is complex. A global integration across US, UK, DE, JP, and AU is an order of magnitude more complex.

The True Cost of DIY SP-API Integration

Before deciding to build your own SP-API integration, understand the real costs beyond just the initial development.

Initial development: $50,000–100,000+. A basic SP-API integration covering orders, inventory, and reporting takes an experienced engineer 3–6 months. At market rates for backend engineers with AWS and API experience, you're looking at $50K minimum. A comprehensive integration covering all endpoints, including Advertising API, pushes well above $100K.

Ongoing maintenance: $2,000–5,000/month. API updates, bug fixes, rate-limit adjustments, and infrastructure costs (servers, databases, monitoring) add up to $24K–60K per year. This isn't optional — an unmaintained integration will break as Amazon updates their API.

Opportunity cost. Every engineering hour spent on SP-API infrastructure is an hour not spent on features that differentiate your business. Unless your competitive advantage specifically depends on custom API integration, the ROI rarely justifies the investment.

When custom integration makes sense. If you're an agency managing 50+ accounts, a large brand with highly specific data pipeline requirements, or a software company building a product on top of Amazon data, custom SP-API integration may be justified. For individual sellers and small agencies, using an existing tool is dramatically more cost-effective.

The No-Code Path

Instead of building on the SP-API directly, use tools that have already invested the millions of engineering hours needed to build, test, and maintain robust API integrations. The question isn't "which tool connects to the API" — they all do. The question is "which tool makes the data most useful for my specific needs?"

Dashboard-based tools (Helium 10, Jungle Scout, Sellerboard) present your SP-API data as charts, tables, and graphs you navigate through traditional web interfaces. You log in, click through menus, and find the data you need. This works well for visual analysis but requires you to know which dashboard has the information you're looking for.

Conversation-based tools (Jarvio) present the same data as answers to questions you ask in natural language. Instead of navigating to the inventory dashboard, filtering by days of supply, and sorting by velocity, you ask: "Which products will run out of stock in the next 14 days?" Same data, different interaction model.

Automation-focused tools go beyond data access and actually take action through the API. Adjusting PPC bids through the Advertising API, pushing listing updates through the Feeds API, and creating restock plans based on inventory velocity data. This is where the SP-API's power truly materialises — not just reading data but acting on it automatically.

What to Look For in SP-API Tools

When evaluating tools built on the SP-API, focus on these differentiators:

• Endpoint coverage. Does the tool connect to the specific API endpoints you need? A PPC tool that doesn't use the Search Term Report endpoint is missing critical data. An inventory tool that doesn't pull inbound shipment data gives incomplete stock pictures.
• Data freshness. How often does the tool sync data from the API? Some tools pull data once daily, others every few hours, and some use the Notifications API for near-real-time updates. For PPC management, fresher data means better optimisation.
• Write capabilities. Can the tool push changes back to Amazon, or is it read-only? A tool that can adjust bids, update listings, and create shipment plans through the API saves hours of manual work compared to one that only shows you data.
• Multi-marketplace support. If you sell internationally, does the tool handle multiple marketplace authentications and data aggregation? Cross-marketplace reporting that combines US, UK, and EU data into unified views requires sophisticated API integration.
• Brand Analytics access. Does the tool pull Brand Analytics and Search Query Performance data? These are some of the most valuable SP-API endpoints, but not all tools implement them.

How Jarvio Connects

Jarvio connects to both the SP-API and the Advertising API, covering the full spectrum of Amazon operations: sales, inventory, advertising, catalogue, finances, and brand analytics. But instead of presenting that data as dashboards you navigate, Jarvio lets you interact through conversation.

Ask "What's my ACoS this month?" and the agent queries the Advertising API, aggregates campaign data, and returns the answer. Ask "Update my listing title for B09KL3" and the agent pushes the change through the Feeds API. Ask "Set up a weekly report comparing my top 10 products" and the agent creates an automated workflow that pulls SP-API data every Monday and delivers it via Slack, email, or Google Sheets.

The API complexity — authentication, rate limits, data processing, error handling — is entirely abstracted. You get the power of direct SP-API access with the simplicity of asking questions in plain English.