Render QR Code With Design

Go to Product

Render a QR code from a content string and a full design — the object the QR Designer’s “Copy JSON” button produces (see the design field for how to get it). Returns the image bytes. Despite the POST verb, which is here only to carry the body, this is a safe and idempotent operation with no side effects: a response may be cached, and a request may be retried — though every retry spends one of the minute’s sixty.

Options

Body

The JSON request body. Pre-filled with an example which is derived from the schema.

Validate JSON
Checks “Body” against the JSON schema of the API. This happens on demand only, i.e. a failed check does not prevent the node from being executed — ultimately, the API itself decides what it accepts.
Body: Validation
Result of the last “Validate JSON” run, i.e. a confirmation or the list of schema violations. Not saved with the node settings.
Response Type
Specify the response type. With Auto-detect – the default – the type is taken from the response itself, which is the appropriate choice whenever the API determines the type based on the request parameters; note that in this case the structure of the output table is only known once the node was executed. The following response types are available:
  • image/svg+xml – SVG markup, UTF-8. Returned for format=svg, the default. Square, sized by size, and self-contained — a logo travels inside it as data, never as a link.
  • image/png – PNG bytes, rasterized from the same SVG at size pixels square. Returned for format=png.
Result Format

Specify how the response should be mapped to the table output. The following formats are available:

Raw Response: Returns the raw response in a single row with the following columns:

  • body: Response body
  • status: HTTP status code
  • x-ratelimit-limit: Requests allowed in the current window.
  • x-ratelimit-remaining: Requests still allowed in the current window.
  • x-ratelimit-reset: Seconds until the window resets and x-ratelimit-remaining returns to x-ratelimit-limit.

Input Ports

Icon
Configuration data.

Output Ports

Icon
Result of the request depending on the selected Result Format.
Icon
Configuration data (this is the same as the input port; it is provided as passthrough for sequentially chaining nodes to declutter your workflow connections).

Popular Predecessors

  • No recommendations found

Popular Successors

  • No recommendations found

Views

This node has no views

Workflows

  • No workflows found

Links

Developers

You want to see the source code for this node? Click the following button and we’ll use our super-powers to find it for you.