Hire an Amazon SP-API Developer: What to Check Before You Sign

What to verify before you hire an Amazon SP-API developer

Calling a REST endpoint is the easy part; any backend developer can do it. What goes wrong in production is different, and it comes down to four things: who owns the developer registration, whether the build sits on APIs Amazon is retiring, how the integration behaves when Amazon throttles it, and how it treats buyer data.

This guide is a checklist for those four, written so an owner or operations lead can run the hiring conversation without reading API reference pages. The facts below were checked against Amazon's own documentation on September 29, 2026.

• Ownership: the developer profile and app credentials live in your account, not the contractor's.
• Currency: new work is built on current API versions, not on ones with a removal date.
• Resilience: throttling is designed for, not discovered after launch.
• Data handling: only the roles the job needs are requested, and credentials are managed properly.

When you actually need an SP-API developer

The Selling Partner API (SP-API) is Amazon's REST API for programmatic access to a seller's data: listings, orders, payments, reports and more. You need a developer when a packaged connector cannot express your logic, for example custom inventory routing across warehouses, feeding orders into your own ERP, or building a tool for other sellers. If a ready-made connector already covers your data flow, a custom build is a maintenance liability you may not need.

The table maps common jobs to the API areas involved, and to where each one tends to go wrong.

Who owns the SP-API developer account?

To call SP-API you need a developer profile in Amazon's Solution Provider Portal and a registered application. Amazon splits developers into two kinds. A private developer builds applications that integrate only their own company with Amazon, and those apps are self-authorized. A public developer builds applications for other sellers, and public apps carry their own authorization limits.

If you are hiring someone to build for your own store, you want to be the private developer. Three details matter for that conversation:

• Only the primary account user can complete registration. A contractor cannot register on your behalf from their side, so the owner has to be involved.
• Approval is Amazon's call. The decision rests on your developer profile, including what the application does and whether it complies with the Acceptable Use Policy and the Data Protection Policy, and Amazon says it cannot detail how eligibility is decided. Amazon also asks you to keep the profile under 500 words, in original wording rather than copied policy text, with your technical team answering the security questions.
• Restricted roles mean PII. Roles that expose personally identifiable information trigger a stricter review. For public developers that includes an architecture review with Amazon's SP-API Solutions Architecture team, which can involve a screen-share demo.

Because approval is a dependency you do not control, write project milestones that do not assume an approval date. Ask the candidate to draft the use-case text with you, and keep the application registration and credentials inside your own account. Amazon provides user management in the Solution Provider Portal, so the developer should work under their own user rather than a shared primary login. The credentials also need rotating over time, and Amazon offers credential rotation notifications through its Application Management API.

Watch for the proposal that says we will use our own developer account for your store. That can be a legitimate public-app arrangement, but it is a rental, not ownership: if the relationship ends, your integration stays with their app.

The API changes a competent developer already knows

Amazon publishes a SP-API deprecation schedule with removal dates. On that schedule, deprecated means the resource is no longer in active development, and removed means calls fail from the removal date. The schedule was last modified on September 9, 2026. These are the entries that matter to a new build, with their status on September 29, 2026:

What changes when Orders v0 becomes v2026-01-01

Orders is the API most integrations touch first, so it is the migration most likely to land on your desk. The replacement is Orders API v2026-01-01, and the differences go beyond renamed calls:

Two practical consequences follow. First, an existing integration written on Orders v0 or XML feeds is a migration project with a hard deadline, not a small fix, so scope and price it that way. Second, any new proposal built on v0 or XML feeds tells you the candidate is working from old tutorials.

A related tell: since October 2, 2023, SP-API no longer requires AWS IAM or AWS Signature Version 4 to call the API. A proposal that budgets days for IAM roles and request signing just to make calls is out of date. AWS is still involved if you use Amazon SQS or EventBridge to receive notifications, so the accurate answer is that IAM left the request path, not the architecture.

What an Amazon SP-API developer costs in 2026

There are two cost lines, and the first one shrank this year. In November 2025 Amazon announced developer fees for SP-API: an annual subscription plus usage fees based on GET call volume. On May 12, 2026 Amazon told developers it will not move forward with the usage and annual fees at this time, so there is no Amazon-side fee to budget as of this article.

Treat the words at this time as a reason to ask candidates how their design would cope with per-call pricing. An integration that listens for notifications instead of polling on a timer costs less to run under any pricing model, and Amazon's own guidance for throttled applications says the same: rely on push notifications instead of polling.

The second line is the developer's fee. Rather than quote rates that go stale, here is what actually moves the price:

Ask for a quote based on written scope. An hourly rate with no scope leaves you carrying the risk of every surprise in that table. If you would rather have someone write the scope with you, Netalith's marketplace integration service covers Amazon SP-API listings, inventory, orders and tracking, priced to the scope of your data flows.

Questions that separate SP-API experience from API tutorials

These questions have checkable answers. Each one maps to behavior described in Amazon's documentation, so a candidate with real production experience answers quickly and specifically.

One point deserves emphasis because it surprises people. For operations on dynamic usage plans, Amazon adjusts rate limits to each selling partner based on business metrics, not on how many requests the application makes, and calling more often does not raise the limit. The fix for a throttled integration is fewer, better-designed calls, not pressure on Amazon.

Freelancer, agency or in-house hire?

The right choice depends less on skill than on continuity, because an SP-API integration needs upkeep. The removal dates in Amazon's schedule stretch across three consecutive years, so a build-and-disappear engagement leaves you stranded at the next retirement.

Contract terms that protect your Amazon integration

• Code in your repository. Source code and infrastructure definitions belong to you and live in an organization you control.
• Registration and credentials in your account. The developer profile, application registration and credentials sit under your business, with the developer added as a user.
• A named deprecation duty. The agreement states who watches Amazon's deprecation schedule and who migrates you before each removal date.
• A runbook. It covers throttling, failed feeds or listing issues, expired credentials, and how to re-authorize.
• Data handling terms. Buyer data is handled consistently with Amazon's Data Protection Policy, and only the roles the work needs are requested.
• Acceptance on real traffic. Payment milestones depend on real orders or listings flowing through production, not only on sandbox demos.

Getting a scoped quote for your Amazon integration

To get a quote you can compare, send the same four facts to every candidate: which Amazon marketplaces you sell on, which data flows you want automated, what system the data must reach, and whether any existing code runs on Orders v0 or XML feeds. Those four answers decide most of the price and most of the risk.

If you want Netalith to scope it, use the free Netalith quote form and select the marketplace integration service.