Connect bunq and StackExchange
Describe what you want to happen between bunq and StackExchange in plain words. HumDay writes the program, proves it on real data, and runs it — no node graph, no field mapping, and no connector to wait for.
What HumDay can do on each side
Read from each provider’s own published API description, in their words.
bunq
421 documented operations. See all bunq operations
- POSTCreate a new DeviceServer providing the installation token in the
/device-server - POSTCreate a new session for a DeviceServer
/session-server - POSTCreate a new public attachment
/attachment-public - POSTUsed to create a sandbox userPerson
/sandbox-user-person - POSTCreate a new debit card request
/user/{userID}/card-debit - POSTUsed to create a sandbox userCompany
/sandbox-user-company
StackExchange
124 documented operations. See all StackExchange operations
- POSTCreate a new comment. Use an accesstoken with writeaccess
/posts/{id}/comments/add - POSTEdit an existing comment
/comments/{id}/edit - POSTDeletes a comment. Use an accesstoken with writeaccess
/comments/{id}/delete - GETCreates a new filter given a list of includes, excludes
/filters/create - GETGet the comments that the users in {ids} have posted in reply
/users/{ids}/comments/{toid} - GETReturns the comments owned by the user associated
/me/comments/{toId}
How a bunq and StackExchange automation gets built
- Describe the outcome. Say what should happen — not which endpoints to call. HumDay works out which operations each side needs.
- Approve the contract. Before anything is built you see exactly what it will do in bunq and StackExchange, and what it will never do.
- See it proven. The program runs and shows you the result before it is allowed near either live account.
- Grant access, then go live. You approve the specific operations it may use on each side — and only those.
Related integrations
- bunq and OData for namespace microsoft.graphintegration
- OData for namespace microsoft.graph and StackExchangeintegration
- bunq and Cloudflareintegration
- Cloudflare and StackExchangeintegration
- bunq and NetBoxintegration
- NetBox and StackExchangeintegration
- bunq and GitHubintegration
- GitHub and StackExchangeintegration
- bunq and Mistintegration
- Mist and StackExchangeintegration
Questions about connecting bunq and StackExchange
- Can bunq connect with StackExchange?
- Yes. HumDay reads both providers' own published API descriptions and derives what each one can do, so neither side needs a hand-built connector before you can use it.
- How do I connect bunq to StackExchange?
- Describe the outcome you want in plain words. HumDay agrees a contract with you saying exactly what it will do, writes the program, and shows you a proof run before either account is touched.
- Do I need to write code to integrate bunq and StackExchange?
- No. There is no node graph to wire up and no field mapping to do. You say what should happen and HumDay works out which operations it needs from each side.
- What can HumDay do across bunq and StackExchange?
- bunq publishes 421 documented operations and StackExchange publishes 124. HumDay only ever uses the specific ones your approved contract needs.
- Is it safe to connect both accounts?
- Your credentials are stored encrypted and never appear in chat, code, or logs. Anything that writes to either bunq or StackExchange is held behind an approval you grant explicitly.
Where this came from
Operations are read from the published API descriptions for bunq and StackExchange. Descriptions are each provider’s own words, not ours.