Work with Sandbox

[Andru4o]

Hello.
Is there a user interface for sandboxing? To create orders, replenish the catalog and more. And then work with this through the API

[charliecode]

@Andru4o If you're referring to a UI like MWS scratchpad? I have not seen anything like that mentioned in the docs. Of course with the new SP-API a sandbox is available, however it's programmatic. In the event you weren't aware of it, it can be found here.

[ShivikaK]

Hello @Andru4o,

Currently we provide a static sandbox environment with mock request and response.

The details of the sandbox environment are provided in the Developer Guide section - The Selling Partner API sandbox

Do let us know if you face any issues or have any further questions.

[Andru4o]

Hello @Andru4o,

Currently we provide a static sandbox environment with mock request and response.

The details of the sandbox environment are provided in the Developer Guide section - The Selling Partner API sandbox

Do let us know if you face any issues or have any further questions.

The main problem is how to create test products, orders and etc to work with it by SP-API . And how we can create a test account to generate this data.

[seanevan]

@Andru4o, our product team is aware of the need for a dynamic sandbox. I will share your feedback with them to help with prioritizing this functionality.

Best regards,
Sean Evans
Manager, Support Engineering

[ericblade]

I was pretty excited when I saw in the documentation, that a sandbox was available. And then when I got my code ready to roll, I investigated it further, and discovered that it is... not actually a sandbox at all.

[charliecode]

@ericblade Any constructive thoughts? You're right, progress could 100% def be made. Would love to hear your thoughts on how that could happen. Wisdom from experts is always valuable.

[ericblade]

Well, I'm hoping that @seanevan 's remark that a "dynamic sandbox" is something that is hopefully being worked on.

A true sandbox would work just like your regular service would, probably with read access to the live catalog (or a recent duplicate of it), and writes deployed to a special copy of the service that is only accessible from the sandbox. So you can actually test all of your inputs, that all of the expected outputs work properly. Not merely a "does my request format work" and "does my response handler work for the one scenario supported".

Just like I'm sure that the API deployment has at the very least a staging and a production instance, there should also be a copy of production running as a sandbox.

For testing "does my code work at a minimal level", there could be a "test" parameter to each service endpoint, that would provide the pregenerated responses, still -- so that automated tests run against sandbox can have predictable results.

Also, a sandbox should have the ability for the user to completely reset it (so after you've accidentally added 10,000 products because something infinite looped unexpectedly, you can quickly reset to a known beginning state :-D )

[github-actions]

This is a very old issue that is probably not getting as much attention as it deserves. We encourage you to check if this is still an issue after the latest release and if you find that this is still a problem, please feel free to open a new issue and make a reference to this one.

[mmdotz]

Has there been any action on this enhancement request?

[gokigoks]

Something similar to the scratchpad would definitely be nice. It would at least make comparing results from both SPAPI and MWS quicker and better.

[ramsesIII]

Is there a Scratchpad for SP-API ?????

[rugved1991]

Hi @ramsesIII,

We currently do not have a Scratchpad for SP API. We have accepted this as a feature request. Please subscribe to our RSS feed on SP API website to receive real time updates on Announcements.

Best,
Rugved
Solutions Architect, SP API.