Integrations

URLs

Use signed or simple URLs for workflows that need a direct render endpoint from another system.

View Pricing

URLs workflow

URLs is set up for teams that need repeatable, template-driven output instead of one-off manual design work.

  • Connect URL-based renders to uploaded assets, approved templates, and API-safe render jobs.
  • Keep all remote image dependencies blocked so production renders use controlled assets only.
  • Use idempotency keys when the same request can be retried by an automation tool.

What this page covers

Use signed or simple URLs for workflows that need a direct render endpoint from another system.

  • Prefer signed URLs when request values should not be editable.
  • Keep secrets out of browser-visible query strings.
  • Use URL workflows for controlled internal tools and lightweight embeds.

Production checklist

Before using this workflow in a campaign, validate the template, expected dimensions, asset ownership, and output access path.

  • Render the same payload three times and compare output hashes for deterministic behavior.
  • Confirm local fonts are present in the approved whitelist before launch.
  • Monitor completed and failed jobs from the logs page during rollout.