You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When building library code based on the specification, the resulting response from the API endpoint cannot be serialized to a correct ListTransactionsResponse object.
The text was updated successfully, but these errors were encountered:
Hi @jasonhebert,
thanks for reaching out!
We are aware of the inconsistencies between the documentation/Swagger model and the actual backend responses and are currently working on fixing this.
Best,
Marc
Selling Partner Developer Services
When making a request to the /finances/2024-06-19/transactions endpoint an invalid 200 response body is returned.
According to the models/finances-api-model/finances_2024-06-19.json model specification the 200 response body shape (
ListTransactionsResponse
) should be as follows:Expected:
{"nextToken": "next-token-value", "transactions": [...]}
Actual:
{"payload": {"transactions": [...], "nextToken": "next-token-value"}, "statusCode": 200}
When building library code based on the specification, the resulting response from the API endpoint cannot be serialized to a correct
ListTransactionsResponse
object.The text was updated successfully, but these errors were encountered: