• Ask the Community

  • API: getting user statement

@MasonChase#89793 I missed an important part, it looks like you're using an oAuth token instead of a "normal" API-key.
Apparently this endpoint is not accesible when you're using an oAuth token.

    I'm sorry, which oauth endpoint are you referring ? what is the URL?

      @MasonChase#89878 The endpoint to create the customer statement CSV. Looks like this one is not accessible if you're using an oAuth token (API-key)

        Anyone from Bunq can comment on this? Documentation is missing a lot of details
        even sandbox URL for oauth wasn't listed .

          @MasonChase

          An oAuth token allows you to perform the following actions:

          • Read only access to the Monetary Accounts.
          • Read access to Payments & Transactions.
          • Create new Payments, but only between Monetary Accounts belonging to the same user.
          • Create new Draft-Payments.
          • Change the primary monetary to which a Card is linked to.
          • Read only access to Request-Inquiries and Request-Responses.

          Creating an CSV statement is not (yet) part of this list. I've reported this to development at bunq.

            Tim changed the title to API: getting user statement.

              @Bastiaan#89908 One could interpret 'read access to accounts/payments/transactions' in different ways. I made a similar mistake when I thought callbacks were available with OAuth, as like statements they provide a kind of read access to transactions...

              It would have been better to explicitly list the endpoints that are available with OAuth.

                I wonder how accounting softwares are able to fetch statement with bunq if this feature is disabled

                  @MasonChase#90441 It is quite easy to create an export manually by using the standard payment endpoints. This is what bunqDesktop does as well when using the custom export page. And not every accounting software uses OAuth over the standard API keys.

                    @Gregory Do you suggest to use Qr Barcode API key generation? this would mean we will get a full feature api key access to the user's account?

                      @MasonChase#90446 No I mean that you can just use the regular payment endpoints which are available with OAuth and create the export yourself. In the end the bunq export is litteraly just the Payment API data stored as CSV.

                        [edit]
                        Okay, I think I understand that by payment endpoint I extract the entire records and then manually generate the CSV, that seems doable. thanks

                        [before-edit]
                        Sorry, I am confused, how to make call to payment endpoint and ask for CSV or MT940 statement for a period of time (start/end date) ?

                          Write a Reply...