ChillisignInstall

Summary

Render email signatures by fetching rendered signature HTML images using a specified authorization token and email address, with optional email client metadata.

Inputs

• Token ID (required) — Authorization token or the string "public" for access.
• Email (required) — Email address whose signature(s) to fetch and render.
• Client — Optional email client name to specify for rendering context.
• Version — Optional version of the email client.

Output shape

a JSON object containing rendered signature data (e.g., rendered signature images or HTML) corresponding to the provided email and token.

The response shape depends on the Chillisign API. Optional query parameters like client and version can alter the rendered output. Supports batching and request options such as proxy, timeout, and ignoring SSL issues for advanced request control.

Examples

Example 1: Render signature for a user's email using a public token

Set 'Token ID' to 'public' and provide the target 'Email'. Leave 'Client' and 'Version' empty for default rendering.