amzn / selling-partner-api-models Goto Github PK

Hello,

will it be possible in the future to update the price and stock over the API directly or are feeds always needed?

best regards,

Michael

Do you support or plan to support webhooks?

It would be very useful to get notified about new orders via a webhook instead of having to pull orders data frequently.

Have a lot simple erros in documentation, for example in https://github.com/amzn/selling-partner-api-docs/blob/main/guides/developer-guide/SellingPartnerApiDeveloperGuide.md#step-4-create-and-sign-your-request

Authorization: AWS4-HMAC-SHA25 Credential=AKIDEXAMPLE/20190430/us-east1/execute-api/aws4_request, SignedHeaders=host;user-agent;x-amz-accesstoken;xamz-date, Signature=5d672d79c15b13162d9279b0855cfba6789a8edb4c82c400e06b5924aEXAMPLE

AWS4-HMAC-SHA25 - correct is AWS4-HMAC-SHA256
x-amz-accesstoken - correct is x-amz-access-token
xamz-date - correct is x-amz-date
AKIDEXAMPLE : don't have explanation what is this value. Perhaps IAM Access Key?

In one line have 3 error ou 4.

I'm trying create the signature, but I am not trusting the information on the page. I lost 4 hours.

The finances-api-model/financesV0.json is not properly formatted.

I tested all of the other models without this error. It happened via SwaggerHub, locally run Swagger open source as well as through my Webstorm OpenAPI plugin, so it appears to def be improperly formatted.

I noticed there were some recent changes made to that file so I also tested the most recent commit and got the same error as well.

Hi all,

We have launched the ability for all developers to register for Selling Partner API!

You can get started by logging in to Seller Central and going to the App &Services -> Develop Apps menu. Once there, you will need to complete your Developer Profile if you have not done so previously, and you can then add a new application.

We're all excited to see what innovations you'll build using SP-API. Our support teams stand ready to assist you with this process - please don't hesitate to ask if you have any questions or concerns.

Best regards,
Sean Evans
Manager, Support Engineering

Welcome to the Selling Partner API (SP-API) docs repo! We're excited to share information about our upcoming new suite of API functionality with developers serving Amazon's selling partners.

To get started, please make sure to watch the repo for notifications as we make announcements via GitHub issues.

Also, we'd love to engage our community for feedback, feature requests, and questions/issues. Please feel free to log an issue and our support engineering team will respond/tag appropriately.

Thank you!
-Evan, PM for Selling Partner API developer experience

Hi,

I don't see anything regarding Usage Plans and Rate Limits for reports api. What are limits?

I cannot use the notifications for finished reports so I have to poll to check if report has finished running, it can cause throttling.
Any plans adding dynamic usage plan to reports?

Thx,

Greg

Previous API generates reports in ISO-8859-1 encoding (NA). As we see now reports in NA have UTF-8 encoding.

1. Is this correct, encoding of Reports will be UTF-8?
2. What encoding of Reports will be for Japanese marketplace?

I'm want create signature to request using AWS SDK PHP, but this resource back x-amz-security-token variable, and SP-API need x-amz-access-token.
Why this API can not use x-amz-security-token?

Hi,
I am trying the new SP-API and I met the issue about authorization when call request.
Step I did:

1. Create IAM user, role, permission.. etc and get access key, secret access key.
2. Use IAM, access key, secret access key to create app and get access token as well as refresh token.
3. Use this access token to sign the API request.

Headers included: host;user-agent;x-amz-access-token;x-amz-date
Canonical request:
"""
GET
/feeds/2020-09-04/feeds

host:sellingpartnerapi-na.amazon.com
user-agent: { user-agent }
x-amz-access-token: { my-access-token }
x-amz-date:20201013T024957Z

host;user-agent;x-amz-access-token;x-amz-date
e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855
"""

Authorize header:
"""
AWS4-HMAC-SHA256 Credential={ access-key-when-create-IAM }/20201013/us-east-1/execute-api/aws4_request, SignedHeaders=host;user-agent;x-amz-access-token;x-amz-date, Signature={ signature }
"""

And I always meet authorize issue:
Response:
"""
{
"errors": [
{
"message": "Access to requested resource is denied.",
"code": "Unauthorized",
"details": ""
}
]
}
"""
There is no detail information. Is this a server side errors or I missed out something when submit the request? Could you please help me to address this issue?

When registering an application I am unable to add an OAuth Redirect URI, after clicking save they never actual save. Therefore after a user approves the developer, there is no redirect to our website. It's allowing my URI such as https://example.com/sp-api-auth but not actually saving it.

Also, you are not able to add a redirect URI for local development. It will not allow http://localhost:4200/sp-api-auth or the like. This is an inconvenience and not friendly to quick development.

Hi everyone!

I'm trying to authenticate with the API. I've gone through all the steps to configure it but I can't authenticate with Postman (see screenshot).

I also made a simple code using the amazon-mws plugin for JS. But I get the same response, access denied.

In the authentication we are using the following:

I appreciate your collaboration.

Edit:

We also tested the Amazon MWS Scratchpad. And we get the same error with the primary and Seller credentials.

I was trying to generate typescript client and encountered this in fbaInventory, I was using swaxios package for this. Interestingly with some other packages it works but I also tried to validate schema here but it still shows the same issues
stack: 'SyntaxError: Swagger schema validation failed. \n' +
" Data does not match any schemas from 'oneOf' at #/paths//fba/inventory/v1/summaries/get/responses/503\n" +
" Data does not match any schemas from 'oneOf' at #/paths//fba/inventory/v1/summaries/get/responses/503/schema\n" +
' Expected type object but found type array at #/schema/properties/payload/properties/granularity/properties/x-docgen-enum-table-extension\n' +
' Additional properties not allowed: properties at #/schema\n' +
' Missing required property: $ref at #/paths//fba/inventory/v1/summaries/get/responses/503\n' +
" Data does not match any schemas from 'oneOf' at #/paths//fba/inventory/v1/summaries/get/responses/500\n" +
" Data does not match any schemas from 'oneOf' at #/paths//fba/inventory/v1/summaries/get/responses/500/schema\n" +
' Expected type object but found type array at #/schema/properties/payload/properties/granularity/properties/x-docgen-enum-table-extension\n' +
' Additional properties not allowed: properties at #/schema\n' +
' Missing required property: $ref at #/paths//fba/inventory/v1/summaries/get/responses/500\n' +
" Data does not match any schemas from 'oneOf' at #/paths//fba/inventory/v1/summaries/get/responses/429\n" +
" Data does not match any schemas from 'oneOf' at #/paths//fba/inventory/v1/summaries/get/responses/429/schema\n" +
' Expected type object but found type array at #/schema/properties/payload/properties/granularity/properties/x-docgen-enum-table-extension\n' +
' Additional properties not allowed: properties at #/schema\n' +
' Missing required property: $ref at #/paths//fba/inventory/v1/summaries/get/responses/429\n' +
" Data does not match any schemas from 'oneOf' at #/paths//fba/inventory/v1/summaries/get/responses/404\n" +
" Data does not match any schemas from 'oneOf' at #/paths//fba/inventory/v1/summaries/get/responses/404/schema\n" +
' Expected type object but found type array at #/schema/properties/payload/properties/granularity/properties/x-docgen-enum-table-extension\n' +
' Additional properties not allowed: properties at #/schema\n' +
' Missing required property: $ref at #/paths//fba/inventory/v1/summaries/get/responses/404\n' +
" Data does not match any schemas from 'oneOf' at #/paths//fba/inventory/v1/summaries/get/responses/403\n" +
" Data does not match any schemas from 'oneOf' at #/paths//fba/inventory/v1/summaries/get/responses/403/schema\n" +
' Expected type object but found type array at #/schema/properties/payload/properties/granularity/properties/x-docgen-enum-table-extension\n' +
' Additional properties not allowed: properties at #/schema\n' +
' Missing required property: $ref at #/paths//fba/inventory/v1/summaries/get/responses/403\n' +
" Data does not match any schemas from 'oneOf' at #/paths//fba/inventory/v1/summaries/get/responses/400\n" +
" Data does not match any schemas from 'oneOf' at #/paths//fba/inventory/v1/summaries/get/responses/400/schema\n" +
' Expected type object but found type array at #/schema/properties/payload/properties/granularity/properties/x-docgen-enum-table-extension\n' +
' Additional properties not allowed: properties at #/schema\n' +
' Missing required property: $ref at #/paths//fba/inventory/v1/summaries/get/responses/400\n' +
" Data does not match any schemas from 'oneOf' at #/paths//fba/inventory/v1/summaries/get/responses/200\n" +
" Data does not match any schemas from 'oneOf' at #/paths//fba/inventory/v1/summaries/get/responses/200/schema\n" +
' Expected type object but found type array at #/schema/properties/payload/properties/granularity/properties/x-docgen-enum-table-extension\n' +
' Additional properties not allowed: properties at #/schema\n' +
' Missing required property: $ref at #/paths//fba/inventory/v1/summaries/get/responses/200\n' +
' \n' +
'JSON_OBJECT_VALIDATION_FAILED\n' +
' at validateSchema (C:\Users\bilal\AppData\Roaming\npm\node_modules\swaxios\node_modules\swagger-parser\lib\validators\schema.js:27:15)\n' +
' at SwaggerParser.validate (C:\Users\bilal\AppData\Roaming\npm\node_modules\swaxios\node_modules\swagger-parser\lib\index.js:155:7)\n' +
'\n' +
'z-schema validation error: JSON_OBJECT_VALIDATION_FAILED\n' +
' at ZSchema.getLastError (C:\Users\bilal\AppData\Roaming\npm\node_modules\swaxios\node_modules\z-schema\src\ZSchema.js:260:13)\n' +
' at validateSchema (C:\Users\bilal\AppData\Roaming\npm\node_modules\swaxios\node_modules\swagger-parser\lib\validators\schema.js:25:23)\n' +
' at SwaggerParser.validate (C:\Users\bilal\AppData\Roaming\npm\node_modules\swaxios\node_modules\swagger-parser\lib\index.js:155:7)',
message: 'Swagger schema validation failed. \n' +
" Data does not match any schemas from 'oneOf' at #/paths//fba/inventory/v1/summaries/get/responses/503\n" +
" Data does not match any schemas from 'oneOf' at #/paths//fba/inventory/v1/summaries/get/responses/503/schema\n" +
' Expected type object but found type array at #/schema/properties/payload/properties/granularity/properties/x-docgen-enum-table-extension\n' +
' Additional properties not allowed: properties at #/schema\n' +
' Missing required property: $ref at #/paths//fba/inventory/v1/summaries/get/responses/503\n' +
" Data does not match any schemas from 'oneOf' at #/paths//fba/inventory/v1/summaries/get/responses/500\n" +
" Data does not match any schemas from 'oneOf' at #/paths//fba/inventory/v1/summaries/get/responses/500/schema\n" +
' Expected type object but found type array at #/schema/properties/payload/properties/granularity/properties/x-docgen-enum-table-extension\n' +
' Additional properties not allowed: properties at #/schema\n' +
' Missing required property: $ref at #/paths//fba/inventory/v1/summaries/get/responses/500\n' +
" Data does not match any schemas from 'oneOf' at #/paths//fba/inventory/v1/summaries/get/responses/429\n" +
" Data does not match any schemas from 'oneOf' at #/paths//fba/inventory/v1/summaries/get/responses/429/schema\n" +
' Expected type object but found type array at #/schema/properties/payload/properties/granularity/properties/x-docgen-enum-table-extension\n' +
' Additional properties not allowed: properties at #/schema\n' +
' Missing required property: $ref at #/paths//fba/inventory/v1/summaries/get/responses/429\n' +
" Data does not match any schemas from 'oneOf' at #/paths//fba/inventory/v1/summaries/get/responses/404\n" +
" Data does not match any schemas from 'oneOf' at #/paths//fba/inventory/v1/summaries/get/responses/404/schema\n" +
' Expected type object but found type array at #/schema/properties/payload/properties/granularity/properties/x-docgen-enum-table-extension\n' +
' Additional properties not allowed: properties at #/schema\n' +
' Missing required property: $ref at #/paths//fba/inventory/v1/summaries/get/responses/404\n' +
" Data does not match any schemas from 'oneOf' at #/paths//fba/inventory/v1/summaries/get/responses/403\n" +
" Data does not match any schemas from 'oneOf' at #/paths//fba/inventory/v1/summaries/get/responses/403/schema\n" +
' Expected type object but found type array at #/schema/properties/payload/properties/granularity/properties/x-docgen-enum-table-extension\n' +
' Additional properties not allowed: properties at #/schema\n' +
' Missing required property: $ref at #/paths//fba/inventory/v1/summaries/get/responses/403\n' +
" Data does not match any schemas from 'oneOf' at #/paths//fba/inventory/v1/summaries/get/responses/400\n" +
" Data does not match any schemas from 'oneOf' at #/paths//fba/inventory/v1/summaries/get/responses/400/schema\n" +
' Expected type object but found type array at #/schema/properties/payload/properties/granularity/properties/x-docgen-enum-table-extension\n' +
' Additional properties not allowed: properties at #/schema\n' +
' Missing required property: $ref at #/paths//fba/inventory/v1/summaries/get/responses/400\n' +
" Data does not match any schemas from 'oneOf' at #/paths//fba/inventory/v1/summaries/get/responses/200\n" +
" Data does not match any schemas from 'oneOf' at #/paths//fba/inventory/v1/summaries/get/responses/200/schema\n" +
' Expected type object but found type array at #/schema/properties/payload/properties/granularity/properties/x-docgen-enum-table-extension\n' +
' Additional properties not allowed: properties at #/schema\n' +
' Missing required property: $ref at #/paths//fba/inventory/v1/summaries/get/responses/200\n' +
' \n' +
'JSON_OBJECT_VALIDATION_FAILED',
details: [
{
code: 'ONE_OF_MISSING',
params: [],
message: "Data does not match any schemas from 'oneOf'",
path: [Array],
schemaId: undefined,
inner: [Array],
[Symbol(z-schema/schema)]: [Object],
[Symbol(z-schema/json)]: [Object]
},
{
code: 'ONE_OF_MISSING',
params: [],
message: "Data does not match any schemas from 'oneOf'",
path: [Array],
schemaId: undefined,
inner: [Array],
[Symbol(z-schema/schema)]: [Object],
[Symbol(z-schema/json)]: [Object]
},
{
code: 'ONE_OF_MISSING',
params: [],
message: "Data does not match any schemas from 'oneOf'",
path: [Array],
schemaId: undefined,
inner: [Array],
[Symbol(z-schema/schema)]: [Object],
[Symbol(z-schema/json)]: [Object]
},
{
code: 'ONE_OF_MISSING',
params: [],
message: "Data does not match any schemas from 'oneOf'",
path: [Array],
schemaId: undefined,
inner: [Array],
[Symbol(z-schema/schema)]: [Object],
[Symbol(z-schema/json)]: [Object]
},
{
code: 'ONE_OF_MISSING',
params: [],
message: "Data does not match any schemas from 'oneOf'",
path: [Array],
schemaId: undefined,
inner: [Array],
[Symbol(z-schema/schema)]: [Object],
[Symbol(z-schema/json)]: [Object]
},
{
code: 'ONE_OF_MISSING',
params: [],
message: "Data does not match any schemas from 'oneOf'",
path: [Array],
schemaId: undefined,
inner: [Array],
[Symbol(z-schema/schema)]: [Object],
[Symbol(z-schema/json)]: [Object]
},
{
code: 'ONE_OF_MISSING',
params: [],
message: "Data does not match any schemas from 'oneOf'",
path: [Array],
schemaId: undefined,
inner: [Array],
[Symbol(z-schema/schema)]: [Object],
[Symbol(z-schema/json)]: [Object]
}
],
toJSON: [Function: toJSON],
name: 'SyntaxError',
toString: [Function: toString]
}

Hi,

What is the best way to get payments and fulfillments informations related to a specified order? For example I see two endpoints dedicated to fulfillments for FBA and FBM stategies (fulfillment-outbound-api and merchant-fulfillment-api) but they do now allow me to fetch fulfillments filtered by either order or order line item.

Also, which endpoint use to fetch payments informations for an order? Is this finances-api enpoint?

Please advice.

Hi all,

Today we removed the API models for Uploads and Messaging. During our beta you have helped us identify issues with these APIs, and we are working on a plan that addresses this feedback to simplify them for the long-term. As always, please let us know if you have any questions or concerns.

Best regards,
Sean Evans
Manager, Support Engineering

Hello, thanks for the incredible updates.
I plan to use a new API for my project, and I wonder if you plan to implement lib for nodejs? (I asked you because I plan to start working on that)

Amazon Team - are you going to be making data from ARA, ARA+P and/or Brand Analytic available via the API?

I'm able to check the status for Acknowledge submitted with no issues but when checking for shipment confirmation the API is crashing.

https://sellingpartnerapi-na.amazon.com/vendor/directFulfillment/transactions/v1/transactions/20201005142211-eaff0231-ba04-4b71-ae53-my_transaction_id

API Returns:
{
"errors": [
{
"code": "InternalFailure",
"message": "We encountered an internal error. Please try again.",
"details": ""
}
]
}

I submitted multiple support tickets and all I get is try again later. What is the real issue?

Hi, I'm super excited with this new API and it will be super useful in our company. In our company we use Node.Js with Typescript for the development and it would be super useful for us to have a client for Node. There is any plan to develop other clients besides Java and C#?

Thanks.

Hi all,

We have updated the Java authorization and authentication library to support IAM role for selling partner applications registered using IAM role and provided an interface to reuse access token generated by LWA Authorization server. For more details please refer to read me

For details about registering application using IAM role please refer to developer guide

Hi there!

I'm really pleased to see that Amazon is embracing the world of having a REST-based API, although I was a little taken back that the documentation remains some of the least developer-friendly I have to engage with (take a look at Stripe, Shopify, or OnBuy for examples of truly wonderful documentation to use).

A few questions:

(1) is the documentation going to be formally published somewhere, to avoid us needing to build it ourselves using Swagger, or attempting to navigate via the GitHub UI?

(2) the rate-limiting documentation is just as unclear as before, except this time there's no easy way of finding out how many tokens we start within our buckets. Also, are different request groups banded together as with the old API, i.e. are all order endpoints bundled into the same rate-limiting group?

(3) following on from the above, the way the documentation is written suggests that 1 getOrder request can be submitted per second (say, downloading 100 orders). The getOrderItems endpoint is then limited to 1 per second also, which means we'll have to fire off 100 requests over the course of 2 minutes. Why can we not expand the getOrder response to include this data? Likewise with the getOrderBuyerInfo.

I'm sure there's a lot of work gone into this, but I'm a little concerned that instead of reimaging the API, it's just been replicated, including the bizarreness of having an ORDER_ACKNOWLEDGEMENT_FEED which actually cancels orders rather than acknowledges them. On the topic of feeds, I see that feeds are still being submitted as XML, despite switching to a JSON based API - why can't we submit the content as such instead of having to endure the 90's concept of an XSD.

In docs under "Authorizing Selling Partner API applications" => "Website Workflow" => "Step 0. Set up your OAuth authorization URIs" when referring to setting up the "Authorize" button it states - "When the seller clicks the button, your website loads an OAuth authorization URI into the browser and the seller is redirected to a Seller Central sign-in page. You get your OAuth authorization URIs when you register your application."

I've registered for the SP-API and the above mentioned OAuth authorization URIs are blank in Seller Central. It is instead an input box for me to add my own. In the docs it does mention using the correct URI per region when linking to your "Authorize" button, but I haven't seen anywhere where the direction is to add them yourself in Seller Central nor which ones to add specifically. The docs do give the following example "https://sellercentral.amazon.com/apps/authorize/consent?application_id=appidexample&state=stateexample" not sure if you would simply switch the top level domain for different regions or what but regardless the documentation doesn't seem to match with the experience. Please let me know if I'm missing something. Thanks!

.

I know it's already been stated that we're not able to complete our Application registration with SP-API until rollout and therefore not able to get a hold of access tokens to make requests to the production endpoint. Is it possible in any way at all to start hitting the sandbox endpoints to better prepare? Thanks!

please delete. I'm getting a 500 error when hitting https://api.amazon.com/auth/o2/

I'm guessing it is not live yet?

In the new version of Reports API, there is no status DONE_NO_DATA. "No Data" reports will be marked as CANCELLED.

Docs: "There are two ways a report can be cancelled: an explicit cancellation request before the report starts processing, or an automatic cancellation if there is no data to return."

If there are 2 possible ways, we need to have the possibility to identify each case. Because there can be different behaviors for these cases.
If it was cancelled because of Throttling, we need to repeat the request in X hours. If the report is cancelled because "no data", we need to mark that there is no data for that specific date range.

This can be a serious issue for the apps that need to import data for past periods.

Example:
If we need to import data of removal orders for the past year. Let's say we will do month by month. And when we do request for April, we got Cancelled report: how to understand if we need to request a report one more time or there is no data in April. The app will stuck :)

Maybe there can be some header with the reason of Cancelation? Or additional field in json response?

Hello,

it would be helpful if the guide has a section included which permissions are need to set for the sqs-queue.
I have an active Subscription for Any Offer Changed but no messages are coming in.
It would also be good when there is function to send a testmessage like it was in the old MWS-API.

best regards,

Michael

In the SP-API docs under "Authorizing Selling Partner API applications" => "Website workflow" => "Step 2" it states:

"The seller views the consent page, reviews the data access requested by your application, and then clicks the Confirm button to continue. The seller can click the Cancel button to exit without authorizing."

The mentioned "Cancel" button is missing. (see attached pic) This happens when testing with "&version=beta". It could also happen in prod but I haven't gotten that far yet.

I'm wondering what the default handling of this should be. I don't notice anything in the docs which states anything other than what is already quoted in this issue. There is no OAuth CancelRedirect URI to add when registering your application. So I'm guessing when the "Cancel" button is actually present and then clicked they'll be redirected back to the "OAuth Redirect URI" without the usual "spapi_oauth_code" in the response. We could of course handle it like that, if that's the case, although better ways to handle it do come to mind. Of course, I cannot test if that is the case since the "Cancel" button is missing. Looking forward to some direction. Thanks guys.

Hi all,

I am writing to clear up some confusion that is reflected in recent GitHub issues. As mentioned in our Hello, World! issue, Selling Partner API is not yet generally available. This means that unless you have been part of our private beta you will not be able to call the API just yet.

Having said that, please watch these repositories - we will have news very soon in that regard!

Best regards,
Sean Evans
Manager, Support Engineering

After generating the Java code for the Solicitations API with Swagger, I got this error in Schema.java: import io.swagger.v3.oas.annotations.media.Schema conflicts with a type defined in the same file.

My solution was to rename the Schema class to SolicitationsSchema.

Steps to reproduce:

1. Generate the Solicitations API Java client code with

    java -jar path/to/swagger-codegen-cli.jar generate \
         -i selling-partner-api-models/models/solicitations-api-model/solicitations.json \
         -l java \
         -t selling-partner-api-models/clients/sellingpartner-api-aa-java/resources/swagger-codegen/templates \
         -o path/to/output/dir

2. Add swagger-annotations as a dependency to build.gradle:
   implementation group: 'io.swagger.core.v3', name: 'swagger-annotations', version: '2.1.5'
3. Copy the io.swagger.client.model package to your SP API project: cp -r path/to/output/dir/src/io path/to/project/src/main/java
4. Run ./gradlew build

I'm using the latest version of amzn/selling-partner-api-models master branch.

I'm facing the following problem:
I have an existing application using MWS and LWA.
Following your announcement (awesome news btw!) I've proceeded with Steps 1-6 in "Registering Your Selling Partner API application" ( https://github.com/amzn/selling-partner-api-docs/blob/main/guides/developer-guide/SellingPartnerApiDeveloperGuide.md#step-6-register-your-application )

Everything is fine until "Viewing your developer information" section. You say "The Developer Central page appears, displaying the IAM ARN associated with your application(s)." But I am not seeing the IAM ARN, nor "Click View under LWA credentials for the application you want." within Seller Central / Developer Central.

Can you help me troubleshoot so that I can finish setting up as a Hybrid? Thank you

We are very familiar with the current MWS ecosystem. As such, we were interested in the net additions to the new API referenced in the announcement.

Specifically, we were looking for information on the vendor and business report API additions. I could not locate any information on these. I'm hoping that this update will support providing the business reports (page views, clicks....) found in the Seller Central UI.

Hello,
I am use MWS API PHP, and I am interested by this new API, but didn't see any information for an PHP Client.
will there be a PHP library for selling-partner-api ?

Hello,

I am trying to use swagger-codegen 3.0.20 to generate an LWA-capable java client. From the root folder of the git checkout I am running:

swagger-codegen generate -l java -i models/finances-api-model/financesV0.json -o java-client -t clients/sellingpartner-api-aa-java/resources/swagger-codegen/templates

Errors out with:

Exception in thread "Thread-1" java.lang.RuntimeException: Could not generate model 'AdjustmentEvent'
at io.swagger.codegen.v3.DefaultGenerator.generateModels(DefaultGenerator.java:451)
at io.swagger.codegen.v3.DefaultGenerator.generate(DefaultGenerator.java:779)
at io.swagger.codegen.v3.cli.cmd.Generate.run(Generate.java:369)
at java.lang.Thread.run(Thread.java:748)
Caused by: java.io.FileNotFoundException: /[omitted]/selling-partner-api-models/clients/sellingpartner-api-aa-java/resources/swagger-codegen/templates/model.mustache
at com.github.jknack.handlebars.io.URLTemplateLoader.sourceAt(URLTemplateLoader.java:70)
at com.github.jknack.handlebars.Handlebars.compile(Handlebars.java:438)
at com.github.jknack.handlebars.Handlebars.compile(Handlebars.java:419)
at io.swagger.codegen.v3.templates.HandlebarTemplateEngine.getHandlebars(HandlebarTemplateEngine.java:48)
at io.swagger.codegen.v3.templates.HandlebarTemplateEngine.getRendered(HandlebarTemplateEngine.java:24)
at io.swagger.codegen.v3.DefaultGenerator.processTemplateToFile(DefaultGenerator.java:795)
at io.swagger.codegen.v3.DefaultGenerator.generateModels(DefaultGenerator.java:438)

Please either fix or modify the phrase in the docs that reads: "Download the latest version of the Swagger Code Generator" to reflect a valid version range; using version 2.4.13, for instance, runs without issue.

Are there any plans to return the hazmat status of an inbound shipment in any of the getShipments, createInboundShipmentPlan, createInboundShipment, or updateInboundShipment operations?

If not, please consider this a feature request : )

Question:
Does creating a new refresh token through the Seller Central UI invalidate previously created tokens?

Seller Central:

Docs:

Hi,

Would be nice if you could create a UML or similar diagram of all models and functions of the API, to give devs a summarized overview of it.
An API reference would be even nicer.

Thanks

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

I just found this is a repeat of issue #672 . Closing the issue based off that.

After looking over this I think the issue may be that I'm not able to register as a SP-API developer in the Developer Central section of Seller Central, as I am already an MWS developer. Could also be that you haven't rolled that live yet. The following is what I experienced when trying to follow the instructions in the docs for "Registering your Selling Partner API application"

I followed all the steps under "Registering your Selling Partner API application". After creating the IAM user, role and policies the last step is to "Register your application".

After registering your application the documentation says you're supposed to be able to view the IAM Role ARN within the Developer Central section of Seller Central. It also mentions "Click View under LWA credentials for the application you want.".

I can see none of this after registering my application. Nor did it ask me for these things when following the instructions to register the application. I'm thinking the issue may be that I was already a registered MWS developer and so I did not have to go through that process before registering the application. Appears to me the Developer Central section of Seller Central is not giving me the options to do things the new SP-API way when registering the application for it.

What do we do if we're already setup as an MWS developer, there are no options to register as a developer for SPA-API.

Hi,
I'd like to register as a developer to the new Selling Partner API (SP-API) by Amazon. This doc says I can do so using Seller Central, but I have a Vendor account, and therefore I need to use the Vendor Central.

Is there a way to do that?

I am a developer of a proprietary CMS and I am using MWS API Reports, Feeds and Orders. For integration I use the C # Client. I would like to start making the change from MWS API to SP API.
In MWS API to authenticate calls I have SellerId, MWSAuthToken, AWSAccessKeyId, Secret Key. AWSAccessKeyId and Secret Key are the values indicated in MWS credentials as attached. Can I use the same values to make SP API calls and how?

Seems very similar to #672 and #679 :
I'm a freelance dev and trying to use SP-API for one of my customers.
I'm not able to see the IAM ARN on my customer's sellercentral account, as described in #679 or here... (my customer also has a MWS application already registered).
Is this a normal behavior ?

PS : my customer failed the assessment because he did respond randomly to the form, not understanding the questions... Now he can't fill the form, everything is greyed out...

Thanks for your help, Regards !

Hi all,

Today we posted use case guides for the Feeds and Reports APIs. These guides provide context and details on how to use these popular APIs, and also explain important changes from the MWS versions of these APIs.

We also uploaded Java helper code for working with encrypted documents, which becomes necessary with the new Feeds and Reports APIs. In the future we will provide this code for other languages as we expand our SDK coverage. As always, we welcome your feedback on the SDK features, patterns, and languages that best support your development efforts.

Best regards,
Sean Evans
Manager, Support Engineering

Hello,
i'm trying to recover the access token (Step 1. Request a Login with Amazon access token) with curl, but the response is '{"error_description":"The authorization grant type is not supported by the authorization server","error":"unsupported_grant_type"}', i have set grant_type to refresh_token, and i have set my refresh_token, i don't understand the error can you help me ?

the request in php:
$cURL = curl_init('https://api.amazon.com');
$data = [
'grant_type' => 'refresh_token',
'refresh_token' => 'Atzr|...',
'client_id' => '...',
'client_secret' => '...'
];
$headers[] = 'Content-Type: application/x-www-form-urlencoded;charset=UTF-8';
$headers[] = 'Host: api.amazon.com';
curl_setopt($cURL, CURLOPT_HTTPHEADER, $headers);
curl_setopt($cURL, CURLOPT_URL, 'https://api.amazon.com/auth/o2/token');
curl_setopt($cURL, CURLOPT_POST, true);
curl_setopt($cURL, CURLOPT_POSTFIELDS, $data);
$response = curl_exec($cURL);

Hi all,

I am writing to clear up some confusion that is reflected in recent GitHub issues. As mentioned in our Hello, World! issue, Selling Partner API is not yet generally available. This means that unless you have been part of our private beta you will not be able to call the API just yet.

Having said that, please watch these repositories - we will have news very soon in that regard!

Best regards,
Sean Evans
Manager, Support Engineering

Hi all,

Today we posted use case guides for the Feeds and Reports APIs. These guides provide context and details on how to use these popular APIs, and also explain important changes from the MWS versions of these APIs.

We also uploaded Java helper code for working with encrypted documents, which becomes necessary with the new Feeds and Reports APIs. In the future we will provide this code for other languages as we expand our SDK coverage. As always, we welcome your feedback on the SDK features, patterns, and languages that best support your development efforts.

Best regards,
Sean Evans
Manager, Support Engineering

Hi all,

We have launched the ability for all developers to register for Selling Partner API!

You can get started by logging in to Seller Central and going to the App &Services -> Develop Apps menu. Once there, you will need to complete your Developer Profile if you have not done so previously, and you can then add a new application.

We're all excited to see what innovations you'll build using SP-API. Our support teams stand ready to assist you with this process - please don't hesitate to ask if you have any questions or concerns.

Best regards,
Sean Evans
Manager, Support Engineering

We maintain professional selling accounts in Europe and other regions purely to access MWS. If I understand correctly, we will continue using these credentials once we transition to the Selling Partner API.

As we do not generate any sales, the accounts get auto downgraded to individual every 90 days. I am wondering if there is any way to avoid this.

Also, would these auto downgrades have any harmful consequences? While I have not tested for a lengthy period, it seems our MWS access and users' auth tokens remain intact after downgrade. Amazon support staff, on the other hand, explained we should lose all access after a downgrade.

(Edited after exchange with support)

message: "Validation failed. Property 'MarkeplaceId' listed as required but does not exist in '/paths/fba/inbound/v0/shipments/{shipmentId}/put/parameters/body'",