Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Finances API version 2024-06-19 /finances/2024-06-19/transactions 200 response invalid #4610

Open
jasonhebert opened this issue Feb 12, 2025 · 2 comments
Assignees

Comments

@jasonhebert
Copy link

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.

@mafge mafge self-assigned this Feb 17, 2025
@mafge
Copy link
Contributor

mafge commented Feb 17, 2025

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

@jasonhebert
Copy link
Author

Thanks @mafge I appreciate the response!!!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants