amzn / selling-partner-api-models

This repository contains OpenAPI models for developers to use when developing software to call Selling Partner APIs.
Apache License 2.0
601 stars 730 forks source link

Where can I start writing an API? #1828

Closed msbeden closed 2 years ago

msbeden commented 3 years ago

Hello,

I have a seller and developer account. We are a software company. Our main goal is to prepare amazon api and attract products with this api, add products, control orders and stock transactions. I need to use Selling Partner API for that too, right? MWS support will be withdrawn?

I've reached the "Registering your application" stage on https://github.com/amzn/selling-partner-api-docs/blob/main/guides/en-US/developer-guide/SellingPartnerApiDeveloperGuide.md.

The data I have now are:

roleArn: arn:aws:iam::.......:role/apiRole

"https://github.com/amzn/selling-partner-api-docs/blob/c76e63c403f7e3b2290cfeb65177af860babb838/guides/en-US/use-case-guides/authorization-api-use-case-guide/authorization-api-use-case-guide-v1.md#Tutorial-Migrate-an-Amazon-MWS-authorization-to-a-Selling-Partner-API-application"

I want to login. What information does this correspond to? Can you help me I've been trying for days.

ShivikaK commented 3 years ago

Hello,

Thank you for raising this issue.

Please refer to below section of the SP API Developer Guide to understand how to connect to SP API after registering your application -

https://github.com/amzn/selling-partner-api-docs/blob/main/guides/en-US/developer-guide/SellingPartnerApiDeveloperGuide.md#connecting-to-the-selling-partner-api

Thanks, Shivika Khare Selling Partner API Developer Support

msbeden commented 3 years ago

Hello there, As you stated, I successfully created the "Step 1. Request a Login with Amazon access token" part. I got access_token as a result of LWA, but when I switched to "Step 2" I started to get stuck. I also added the header part in "Step 3".

Use the "GET" method in the document. But it also says "PUT" method, I didn't know which one to use. I tried both. I didn't get results. I am getting an error as in the picture.

What is the "shipmentId1" variable? Are we creating a fixed value ourselves?

I'm waiting for your help. Good work.

2021-09-08_094039 2021-09-08_094356

mburakgunduz commented 3 years ago

Can you reply urgently? I am also having the same problem.

ShivikaK commented 3 years ago

Hello @msbeden

The shipmentId1 is just an example for the value of Shipment ID path variable provided in our documentation.

I would suggest referring to sandbox section to test connection to any API section of SP API by connecting to the sandbox endpoints.

https://github.com/amzn/selling-partner-api-docs/blob/main/guides/en-US/developer-guide/SellingPartnerApiDeveloperGuide.md#the-selling-partner-api-sandbox

Thanks, Shivika Khare Selling Partner API Developer Support

msbeden commented 3 years ago

Hello.

I still didn't understand anything from the documentation available on Github. I'm trying to solve my operations with a ready-made php library.

I am trying to login with "https://github.com/amzn/selling-partner-api-models/tree/main/models/authorization-api-model". But I couldn't find where to get MWS token.

I developed an application under the "https://sellercentral.amazon.com.tr/sellingpartner/developerconsole/ref=xx_DevCon_dnav_xx" page. After this app is published on Amazon Appstore, I need to get MWS token by giving access to this app from my seller account, am I right?

vdanyliv commented 3 years ago

@msbeden I wrote several articles about SP-API, maybe you found something useful here

Amazon selling partner API (SPAPI) — how to quickly and simply integrate with new API (Part 1)

Amazon selling partner API (SPAPI) — how to quickly and simply integrate with new API (Part 2)

Amazon selling partner API (SPAPI) — How to implement reports generation workflow with AWS Step Function (Part 1)

github-actions[bot] commented 2 years ago

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.