Get a specific event for a given user in bunq
A documented bunq operation that only reads, so it can watch for changes without altering anything. Describe what you want to happen and HumDay builds it.
What this operation does
Get a specific event for a given user.
- GETReads data · event
public-api.sandbox.bunq.com/user/{userID}/event/{itemId}
How HumDay uses it
- You describe the outcome. Not this operation by name — what you want to happen. HumDay works out which operations it needs.
- The contract names it. Before anything is built, you see exactly which bunq operations the program may use, and this is one of them.
- You approve access. Read-only access is still yours to grant, and still limited to what the contract needs.
Other bunq operations
- Create a new DeviceServer providing the installation token in thePOST · changes data
- Create a new session for a DeviceServerPOST · changes data
- Create a new public attachmentPOST · changes data
- Used to create a sandbox userPersonPOST · changes data
- Create a new debit card requestPOST · changes data
- Used to create a sandbox userCompanyPOST · changes data
- Create a new credit card requestPOST · changes data
- Create new MonetaryAccountBankPOST · changes data
Questions
- Can HumDay get a specific event for a given user in bunq?
- Yes. This operation is published in bunq's own API description, so HumDay can use it without a hand-built connector — once you have approved it for your automation.
- Does this change anything in my bunq account?
- No. This is a read-only operation, so it can be used to watch for changes or fetch data without altering anything in bunq.
- Do I need to write code?
- No. You describe the outcome you want in plain words. HumDay agrees a contract with you, writes the program, and shows you a proof run before anything touches your bunq account.
Where this came from
Read from a published API description for bunq at raw.githubusercontent.com/bunq/doc/master/swagger.json. The description above is the provider’s own wording, not ours. Last published 2023-03-06.