Bunq Signing
AI-generatedSummary
Signs a user-supplied string with the private key from the bunqApi credential using RSA-SHA256 and returns the base64 signature alongside the original body. Runs locally with no bunq API call.
Inputs
- Request Body (required) — The string to sign (any text, typically the exact JSON payload to be sent to bunq). Multi-line field, evaluated per input item, so expressions can pull data from earlier nodes. Sign the exact string you will send, since any change alters the signature.
Output shape
One output item per input item, each with json.body (the string that was signed) and json.signature (base64-encoded RSA-SHA256 signature). Items are paired to their input items.
The private key is read from the required bunqApi credential (privateKey, PEM). If signing fails (e.g. invalid key) the node throws a NodeApiError, or with Continue On Fail enabled it emits an item with json.error instead. The signature is meant to be used as the X-Bunq-Client-Signature header in custom requests.
Examples
Example 1: Sign a JSON payload for a custom HTTP Request call to bunq
Set Request Body to an expression such as {{ JSON.stringify($json.payload) }}, then map the output signature to the X-Bunq-Client-Signature header in an HTTP Request node.