Skip to main content

More raw transactions data in API destination

Feature Request

I think it would be very helpful to expand REST API to return more raw transaction information. It could be an optional field switch, something rawData=true and then API response includes the full transaction data Lunchflow has(iban’s, currency exchange info etc) alongside everything else. I know Lunchflow already has the data I’m looking it as I can see it in the Data preview when configuring the “Connection” in the Web UI. Its also available in the Google sheets output “Raw Data” tab, I would just like it to be available via the API too.

Posted by Dar Donkov ·
Status: Completed24 comments

Log in to comment and vote

Comments24

  • Amr from Lunch Flow changed status to Completed
    Team•

    Oct 18

    Pinned

    Hey all 👋

    Been a long time coming, but happy to share that the API now includes an include_raw query parameter to pull all the raw data from the provider for both accounts and transactions 😄

    Feel free to give it a try, and keep the feedback coming!

  • Carla Notarbot

    •

    Dec 15, 2025

    Upvoting. For our usecase, we try to automate conciliation against invoices. The more info we have available the more cases we can automate with certainty. We also use LLM’s heavily so we don’t mind if each provider structures the data in a different way

    • Amr from Lunch Flow

      Team•

      Dec 16, 2025

      That’s very helpful context, thanks for sharing, @Carla! I was planning on only releasing this if I could ensure it’s fully type-safe in the open API spec, so that LLM point is a good insight.

      At the moment, I’m slowly expanding the raw data available in the UI, starting with MX, which you can now see.

      If there’re specific providers you’re interested in, let me know 😄

  • Glen Nicholls

    •

    Dec 14, 2025

    One of my use-cases is venmo where I want to get at the originalDescription along with user ID information to properly set the merchant and description.

  • Amr

    •

    Oct 4, 2025

    Hey @Dar 👋

    Thank you very much for the feedback! Mind sharing a bit more about the fields you need for your use case?

    Also, If you're using Gocardless, you can use templates to fit multiple fields in the notes for example. I know it's not as flexible, but might be a viable workaround in the meantime 😀

  • PT

    •

    Oct 19, 2025

    Apologies if this should go elsewhere, but it felt relevant to this post.

    I noticed that since the description in the API uses the Notes field in the Data Connection, it might be useful to have an actual ‘Notes’ option in the API (and therefore an extra field in the Data Connection config) to allow some of that additional information to be pulled down.

    It’s got to be a difficult balance between keeping the API simple - a huge bonus - and providing enough information.

  • Olivier Cloux

    •

    Feb 21

    Such a cool tool, frustrating that I can’t get raw data! As others said, it’s not important that the data is different across providers, this is something I can fix myself. Even if it’s an additional endpoint, or something that is not "core”, would work fine. I see my transactions have so much data available (e.g. 3 different date/times), but I’m limited to choosing one. All are relevant!

    • Amr from Lunch Flow

      Team•

      Feb 23

      Noted, thanks for sharing that feedback, @Olivier !

  • Issam GUESMI

    •

    Mar 5

    Hello Amr

    We NEED the raw data ASAP.
    We subscribed thinking we could get all the data we want.
    We are using your service for invoice reconciliation, without the raw it is useless.
    Please provide an answer if you are planning this, and ETA.
    I see the OP is 5 month old, if there is no hope we’d be forced to switch services.
    Thanks for your attention to this matter.

    • Issam GUESMI

      •

      Mar 6

      I tried using the Template feature to map the REMITTANCE to description
      it does not work…

      • Amr from Lunch Flow

        Team•

        Mar 6

        Thanks for checking in @Issam , afraid there’s no ETA I can share at the moment, but it’s definetly on the plan, there’re however quite a few higher priority items for me to tackle before then, I’ll let you know once that lands.

        The templates should be working though, will reach out to get more details, and perhaps this is something that can be resolved.

        • Issam GUESMI

          •

          Mar 8

          Thanks for your answer
          Here is what i have done, maybe i am wrong ?
          On the configuration page of an account, Tab Description :

          —
          Advanced Mode (Template) : OFF
          Dropdown : Remittance Information Unstructured Array
          —

          Sadly the description field is not populated with the full remittance information, it stays empty.

          Any hints ?

          • Amr from Lunch Flow

            Team•

            Mar 8

            That sounds like a bug indeed, will look into resolving that. in the meantime, can you turn on advanced mode and try this in the template field?

            it.remittanceInformationUnstructuredArray

            • Issam GUESMI

              •

              Mar 9

              Hello Amr
              it works with the advanced mode and it.remittanceInformationUnstructuredArray
              Thank you !!

  • Kira

    •

    Jul 9

    •

    Merged request

    Expose both Posted Date (bookingDate) and Transaction Date (valueDate) in GET /transactions API

    Currently, the GET /api/v1/accounts/{accountId}/transactions endpoint returns a single top-level date field. While the system processes multiple date fields from bank data (like valueDate and bookingDate) to determine this value 3, API consumers cannot access both dates separately, as far as I can tell 4

    It would be useful if the returned both the raw transaction occurrence date (value date) and the posted date (booking date) as distinct fields in the response to allow API consumers to decide which date is most relevant for their specific integration and reconciliation use cases.

  • Noah Kottenhahn

    •

    Jul 21

    I urgently need the IBANs for transactions, if they’re available.

    This is required for identifying whether a transaction is a simple payment (in which case the IBAN would not be of interest - I would use the merchant name as-is) or a transfer between pre-configured accounts. There is curently no way of accurately identifying such transfers other than hardcoding transaction descriptions since there is debtor/creditor name overlap between these acounts.

    • Amr from Lunch Flow

      Team•

      Jul 21

      Hey @Noah 👋

      Thanks for the additional context. have you tried adjusting the merchant and description fields through the account configuration? You can use templates to include any information from the raw data there.

      • Noah Kottenhahn

        •

        Jul 22

        Yes I did. But it seems (at least according to the raw data preview in the template editor) that no field contains any IBAN information.

        After all, this feature request asks for adding more information to the raw data. I, for one, would be incredibly happy if the raw data contained more information. Then I could use that in templates of course.

        • Amr from Lunch Flow

          Team•

          Jul 22

          I see what you mean 😄 There’s a slight miscommunication here, the request was more on surfacing the raw transaction information we currently have access to. Adding more raw data likely wouldn’t be possible unless we switch providers and they offer more data, but it’s not something we can control.

          Hopefully that makes sense.