Addition of Transactions List Endpoint to existing Airbyte Connector

[Harmaton]

What

This PR introduces a new endpoint to retrieve a list of transactions from the amazon seller api. It addresses the need for users to view their transaction history efficiently and provides proper documentation and configuration for the new feature.

How

• Created a new Transaction List Schema in ListTransaction.json to handle GET requests for transaction lists
• Implemented the stream logic in streams.py
• Added appropriate configuration of the stream in source.py

[zerobearing2]

@Harmaton I'm attempting to build the source-amazon-seller-partner connector locally, and test run it. The build works as expected, installed into local airbyte cluster, and set the connector version to dev, per the airbyte docs.

However, when attempting to retrieve the schema (creating a connection), it fails. See attached log dump of the exeception.
discover_schema-failure-bbef56cf-2d97-4a8d-920e-4e3535992e60.txt

Switching the connector version back to 4.4.4 (the latest) works. So either I'm doing something incorrectly, or there is a bug. Are you able to test run locally? If so, do you have instruction on getting it running properly?

FWIW: I rebased this branch with latest master from airbyte repo to ensure its latest.

/cc @revans

[zerobearing2]

Does it make sense to name this stream FinanceTransactions instead of ListTransactions? Feels like ListTransactions is a little ambiguous. Thoughts?

[Harmaton]

Do you mind temporarily providing me with credentials so I can generate the exact schema I wish to get ? Its quite large and complex to do manually

[Harmaton]

@zerobearing2

[zerobearing2]

@Harmaton I can't provide any live credentials, sorry. I was just researching how to provide sandbox access. I'm unfamiliar with seller central sandbox, so not sure exactly how to grant access yet. However, it seems the sandbox just responds with a "mocked" response. The finance mocked response comes from github here: https://github.com/amzn/selling-partner-api-models/blob/main/models/finances-api-model/finances_2024-06-19.json

Is that something you could use? I will continue looking at how to provide temporary sandbox credentials and reply when I have something to share.

[Harmaton]

Use the following Instruction to run the tests. I made a few changes to fix the schema issues causing the error. I decided to keep the prior naming to match the amazon documentation naming.

Here is the Spec.json file to help with config for local dev.

Thanks!

[zerobearing2]

Use the following Instruction to run the tests. I made a few changes to fix the schema issues causing the error. I decided to keep the prior naming to match the amazon documentation naming.

Here is the Spec.json file to help with config for local dev.

Thanks!

Awesome, will try again running locally and report back. Thanks!

[zerobearing2]

@Harmaton after rebuilding from latest, still seems to be having same issue. 🤔
discover_schema-failure-30a75cb5-2159-4f19-a2d1-7455d5382931.txt

[Harmaton]

I updated the schema in the code with the reference to the json schema in the documentation. Please run this test. I atleast expect a different error if any. Iam almost done securing my own credentials if I need to do any other test on my end. Thanks!

[zerobearing2]

@Harmaton I was able to get the schema to run now, however it doesn't look correct. Missing fields and why would pagination nextToken be included?

[Harmaton]

I spotted the error and fixed it with the latest commit.

[zerobearing2]

Still only showing the transactions array instead of the actual transactions fields.

[Harmaton]

I would appreciate if you could please run the LAST test for me. If it does not sync then I will get to use my credentials by tomorrow. I am however confident this was the last iteration . @zerobearing2

[Harmaton]

@zerobearing2 Can you confirm that you can now see the field listings ?

[zerobearing2]

@zerobearing2 Can you confirm that you can now see the field listings ?

replied in slack