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

Build transaction enrichment action / flow (with Synth API) #834

Open
zachgoll opened this issue Jun 4, 2024 · 0 comments
Open

Build transaction enrichment action / flow (with Synth API) #834

zachgoll opened this issue Jun 4, 2024 · 0 comments
Labels
❔ Needs scoping Requirements need to be discussed and finalized before working on this 🚀 Feature

Comments

@zachgoll
Copy link
Collaborator

zachgoll commented Jun 4, 2024

Overview

The primary goal of this issue is to build a backend flow that reads through a user's list of transactions, calls the Synth API for each to fetch enhanced merchant logos and data and more:

https://docs.synthfinance.com/reference/enrich-transaction

Scoping

This issue does not have hard requirements and still needs to be scoped. Some ideas for this include:

  • Nature: this should most likely be a background job
  • Trigger: to start, we should probably require user action to trigger this flow. The main reason for this is because this will consume API credits and we don't yet have a good UI for users to manage their data providers and API usage.
    • User can manually trigger enrichment for a single transaction
    • User can manually trigger enrichment for selected (or all) transactions
  • UI/UX: this should probably be an "action" provided in the transaction row menu, similar to other actions like "edit", "delete", etc.
@zachgoll zachgoll converted this from a draft issue Jun 4, 2024
@zachgoll zachgoll changed the title Enrich transactions with Synth API Build transaction enrichment action / flow (with Synth API) Jun 4, 2024
@zachgoll zachgoll moved this from Ready to Planning in Transaction Management Jun 4, 2024
@zachgoll zachgoll added the ❔ Needs scoping Requirements need to be discussed and finalized before working on this label Jun 4, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
❔ Needs scoping Requirements need to be discussed and finalized before working on this 🚀 Feature
Projects
Status: Planning
Development

No branches or pull requests

1 participant