[BUG] [SP-API] [Issue] Incorrect type of `payloadVersion` in `notifications.createSubscription` response

[achie27]

I'm submitting a...

[ ] Regression (a behavior that used to work and stopped working in a new release)
[x] Bug report  
[ ] Feature request
[ ] Documentation issue or request
[ ] Other... Please describe:

SP-API Name and Version or Report/Feed Type

Notifications > createSubscription

Expected Behavior

payloadVersion in the response should be a string and not a float

Current Behavior

This happens when subscribing sellers to LISTINGS_ITEM_ISSUES_CHANGE (which uses the EventBridge workflow). Here's one response I received on prod -

{
  "payload": {
    "destinationId": "798267b8-2540-4f27-a439-d649d3345fe3",
    "payloadVersion": 1.0,
    "subscriptionId": "3de8dec4-6ec5-43f1-bc65-7ed2f8baca89"
  }
}

And here's the headers to investigate -

X-Amz-Apigw-Id: aP21pHIroAMFyig=
X-Amzn-Requestid: f89fbdde-6a49-475b-b60e-d2ff9916ffc3
X-Amzn-Trace-Id: Root=1-634fd1bd-10adf26330f3771559a99e65

Context/Screenshots

• Although the subscription is created successfully, due to this incorrect type, the OpenAPI generated code errors out when unmarshalling the response and short-circuiting a lot of program logic
  • Exact error in Go - json: cannot unmarshal number into Go struct field Subscription.payload.payloadVersion of type string
• I'm also creating subscriptions for ORDER_STATUS_CHANGE (which uses the SQS workflow) for which payloadVersion's type is correct

  • {
    "payload": {
        "subscriptionId": "72339084-4e2e-4a0d-aae6-271cacfd3560",
        "destinationId": "bfb3d425-122a-4baa-9410-94f98e4c368b",
        "payloadVersion": "1.0"
    }
    }

    X-Amz-Apigw-Id: aP767F9qIAMFweg=
    X-Amzn-Requestid: 70823800-d16b-4e52-8536-0487067de801
    X-Amzn-Trace-Id: Root=1-634fd9df-68b30a8a63061f8b163a2722

    Your Environment

    Go, with API code generated using the OpenAPI models

[github-actions[bot]]

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.

[github-actions[bot]]

closed for inactivity