Quick Start

1. Sign up for a SignStack account.
2. Open the Studio at signstack.ai.

1. Sign up for a SignStack account.
2. Install Node.js 18+ and the CLI:

   npm install -g signstack
   

   bash
3. Authenticate the CLI:

   signstack auth login
   

   bash

From the home screen, click New Contract and describe what you want:

"A consulting services agreement where the company signs first, then the consultant countersigns. Capture name, email, rate, and start date for the consultant."

Studio generates the primitives your contract needs. You land in the preview when it's done.

From any directory, describe the contract inline:

signstack generate "a consulting agreement where the company signs first,
then the consultant countersigns"

The CLI writes YAML files for each primitive the contract needs into a new project folder — blueprint, schemas, assets, templates, and custom functions if any.

The preview panel is already open with a rendered PDF. Pick a different scenario from the dropdown to re-render, or hit refresh after you make edits.

signstack generate prints the exact preview command for the blueprint it built. It'll look like this:

signstack preview <blueprint-key>@<version> --scenario <scenario-key>

Run it to open the rendered PDF locally. Re-run after edits.

Click Publish. Your draft is cut to a new version and the blueprint — plus every schema, template, asset, and function it depends on — is frozen at that version.

signstack push <blueprint-key>@<version>

The CLI publishes the blueprint and every primitive it depends on, cutting each to a new immutable version. signstack generate prints the exact push command.

Open the blueprint, click Run, pick a scenario (or fill in the data form), and submit. The workflow starts immediately and appears in the workflow monitor.

Best for: one-off runs, testing, demos, giving non-developers a way to kick things off.

signstack generate also prints the exact run command, using one of the generated scenarios:

signstack run <blueprint-key>@<version> --scenario <scenario-key>

The CLI calls the same API the Studio does.

Best for: scripted end-to-end tests, CI, running workflows from the same repo that holds your primitives.

curl -X POST https://api.signstack.ai/v1/orgs/{orgId}/namespaces/{namespaceKey}/workflows \
  -H "Authorization: Bearer <TOKEN>" \
  -H "Content-Type: application/json" \
  -d '{
    "blueprintKey": "consulting_services",
    "blueprintVersion": "1.0.0",
    "data": {
      "consultant": {
        "firstName": "Jane", "lastName": "Doe",
        "email": "jane@example.com", "rate": 150, "startDate": "2026-04-01"
      },
      "company": {
        "name": "Acme Corp",
        "representative": { "name": "Bob Smith", "email": "bob@acme.com" }
      }
    }
  }'

Best for: production — your application triggers workflows directly from the business event that should cause them (a deal closed, an employee hired).

See Namespaces for why namespaceKey is in every path.