SigAPI.com

Choose your next step

A practical signature resource library

Start with the question in front of you. These reading paths and small examples connect signature design, developer workflows, privacy, and platform identity.

Pick a useful starting point

I’m designing a signature

Start with the information your recipient needs. Then choose a layout, make the links descriptive, and check the finished message.

Signature essentials

I’m connecting a workflow

Separate profile data from templates and mailbox configuration. Review the authorization boundary and plan a reversible rollout.

API architecture

I’m reviewing tracking

Trace what an image request represents. Account for privacy features, document the limits, and choose outcomes that inform a decision.

Pixel fundamentals

I’m organizing a public profile

Keep the same recognizable identity across different fields, then give each audience a clear and relevant next step.

Platform guide

A simple HTML starting pattern

This signature example keeps contact information as text and uses a small table with inline styles. It has no tracking pixel. Treat it as a pattern to adapt, then test the resulting message in your actual email clients.

<table role="presentation" cellpadding="0" cellspacing="0"
  style="font:14px Arial,sans-serif;color:#11132a">
  <tr><td style="border-left:3px solid #7150e2;padding-left:16px">
    <strong style="font-size:20px">SigAPI.com</strong><br>
    Signature guides &amp; API field notes<br>
    <a href="mailto:[email protected]"
      style="color:#5735ad">[email protected]</a><br>
    <a href="https://sigapi.com/"
      style="color:#5735ad">Explore SigAPI.com</a>
  </td></tr>
</table>
Download the HTML example as text

A structured profile example

Before choosing a renderer, identify the public fields the signature actually needs. The example below is data only: it does not submit information, call an endpoint, or configure a mailbox. Keep template styling and any credentials separate.

{
  "displayName": "SigAPI.com",
  "role": "Signature guides and API field notes",
  "email": "[email protected]",
  "website": "https://sigapi.com/",
  "templateVersion": "1"
}

Download the profile JSON and read the signature API architecture guide to understand its place in a wider workflow.

Before you publish a signature

  1. Confirm the information. Check names, roles, contact destinations, and ownership of linked pages.
  2. Review the rendered result. Look for missing fields, unwanted wrapping, and unreadable links.
  3. Send a real test. Review the received email on desktop and mobile, with images hidden, and in a reply.
  4. Review measurement choices. Document what any event can establish and whether collecting it serves a defined purpose.
  5. Keep a maintenance path. Save the approved version, name an owner, and revisit the signature when details change.

For a team rollout, follow the team signature management guide. For a platform profile, use the integration notes.

Follow the guidebook

Browse all ten articles in SigAPI Field Notes, choose a category, or follow a specific topic. Feed readers can subscribe through the RSS feed or the Atom feed. Both include complete article text.

Have a correction or a question the guidebook should address? Email [email protected] with the relevant page and enough context to make the issue reproducible.