Skip to main content
Templates define the documents and signer configuration for a signing package. Flows define the guided walkthrough experience presented to signers. Both are scoped to a location and managed through the endpoints below. All endpoints in this group require a Clerk session JWT and enforce RBAC based on your session’s module tiers. Managers see only templates and flows at locations they can access. Admins receive global access, capped at 500 rows per list response. Check caps.manager.templates and caps.manager.flows in your session payload to determine which operations are available to your account before calling these routes.

Templates

List templates

Returns templates for the locations in your scope. Managers can optionally filter by location. Admins receive all templates globally (capped at 500). Results are ordered by id ascending.
Required tier: templates at "read" or above, or admin.
string
Numeric location ID to filter results. Managers specifying a location outside their scope receive 403.

Response

array
required
Array of signing.templates rows.
string
required
"managed" for managers scoped to their accessible locations, or "global" for admins.

Error responses


Get one template

Returns a single signing.templates row. The template’s location must be in your scope.
Required tier: templates at "read" or above, or admin.
string
required
Numeric template ID.

Response

The signing.templates row for the requested template.

Error responses


Update a template

Partially updates a template’s name and/or active flag. You must supply at least one field. The template’s location must be in your scope.
Required tier: templates at "write" or above, or admin.
string
required
Numeric template ID.
string
New display name for the template. Minimum 1 character, maximum 500 characters.
boolean
Set to false to deactivate the template (prevents it from being selected when creating new signing packages) or true to re-activate it.

Response

object
required
The updated signing.templates row.

Error responses


Duplicate a template

Creates a copy of an existing template at the same location. The new template receives a name of "Copy of <original name>" and is otherwise an exact clone of the source row (pages count, signer numbers, explanation IDs, processing flags, tag, etc.). The completedSigningsCount on the copy is reset to 0.
Required tier: templates at "write" or above, or admin.
string
required
Numeric ID of the template to clone.
No request body.

Response

object
required
The newly created signing.templates row representing the copy. Its id and createdAt/updatedAt are new; its locationId matches the source.

Error responses


Flows

Flows define the guided signing walkthrough sequence for a package—the order of explanation steps, the signer prompts, and any location-specific configuration. When you create a signing package with a flowId, the flow at that location determines the signer experience.

List flows

Returns flows for the locations in your scope, optionally filtered by location. Admins receive all flows globally (capped at 500). Results are ordered by id ascending.
Required tier: flows at "read" or above, or admin.
string
Numeric location ID to filter results. Managers specifying a location outside their scope receive 403.

Response

array
required
Array of signing.flows rows in your scope.
string
required
"managed" for scoped manager access, or "global" for admin access.

Error responses


Get one flow

Returns a single signing.flows row. The flow’s location must be in your scope.
Required tier: flows at "read" or above, or admin.
string
required
Numeric flow ID.

Response

The signing.flows row for the requested flow.

Error responses


Using templates and flows together

When creating a signing package via POST /v1/signing/manager/signings, you can supply a flowId to associate a specific walkthrough flow with the package. The flowId must reference a flow at the same location as the locationId you specify—a mismatch returns 400. Templates are not directly referenced when creating a package via API. They are used by the platform to populate a package’s documents. Refer to your integration documentation for how templates are applied during package setup.
Neither templates nor flows can currently be created or deleted through the API. Use the Safeclose manager UI to create new templates and flows, then reference them by ID in API calls.