Docusign → Embedded templates

This guide helps you move Docusign template creation and embedded template editing to Formable. You still upload a document, open an editor for field placement, and reuse a templateId when sending. Formable collapses that into a multipart upload plus an editUrl iframe, without OAuth account paths or Anchor/AutoPlace tabs in the create payload. When templates are ready, continue with Docusign → Embedded signing to send envelopes for signature.

New to Formable? Complete the Embedded templates walkthrough first, then use this page as a translation layer from Docusign templates and template edit views.

Prefer a white-glove migration? Email matt@formabledocs.com and we’ll handle moving your Docusign integration to the Formable API.

What you’re moving

In Docusign apps you typically:

Create or update a template (API and/or web UI) under an account
Define tabs with coordinates, anchors, or the sender / template UI
Optionally open an embedded template edit view (TemplateViews:createEdit and similar) so users adjust fields in your product
Send envelopes from that templateId, often with templateRoles and tab values

In Formable you:

POST /v1/templates with the file
Embed editUrl so users place fields in your product
Copy each field’s id for later prefills
Create signature requests with that templateId and a signers array

You are migrating document preparation and in-product editing. Envelope send and recipient views live on the paired signing guide.

Recommended order of work

Get a Formable API key

Create an organization and key in Settings. See Authentication.

Re-upload each template document

Call POST /v1/templates with PDF or Word files (max 40MB).

Replace template edit views

Embed editUrl from create, or POST .../edit-url when it expires.

Map tab labels to fieldIds

Place fields in the Formable editor and update prefill code to use fieldId instead of Docusign tabLabel / anchors.

Send with the new templateId

Continue with embedded signing migration.

What’s similar

The high-level template model still matches Docusign:

Upload once, get a reusable template ID, send many times.
Users can edit field placement inside your product via a short-lived editor URL.
Prefills happen at send time against named field identifiers.
Template editing and signing use the same auth story on Formable (one Bearer key for both).

If your Docusign product already embeds a template editor and stores templateId for later envelope creates, keep that product flow. Rebuild how the file is uploaded and how the editor URL is minted.

What’s different

Plan for these Docusign-specific patterns that do not map 1:1:

Area	Docusign	Formable
Auth	OAuth + account-scoped template APIs	Bearer `fmbl_…`; organization from the key
Roles on create	Template roles defined up front	Optional `signer_roles` on create; assign roles to fields in the editor; pass `signers[].role` at send time
Tab placement	Coordinates, Anchor / AutoPlace strings, or UI	Visual placement in Formable’s editor
Prefill keys	`tabLabel` / tab groups on roles	`fieldId` from the Formable editor
Edit view	Template edit view API with account path	`editTemplateAccess.editUrl` or `POST .../edit-url`
Editor TTL	Varies by view	Default about 1 day; mint just in time

Anchor strings and absolute coordinates in create-envelope payloads do not carry over. Recreate positions in the Formable editor, then store the new fieldIds in your database or config.

Concept map

Docusign	Formable	Notes
Template	Template	Upload once, reuse `templateId`.
Tabs (SignHere, Text, DateSigned, …)	Fields (Signature, Text, Date, …)	Placed in Formable’s visual editor.
Template edit view URL	`editUrl`	Embed in an iframe. Expires (default 1 day).
Anchor / AutoPlace tabs	Visual placement in the editor	Recreate positions in the UI; prefill by `fieldId`.
Template roles	Optional `signer_roles` on create + field placement in the editor	Pass matching `signers[].role` at send time.

Endpoint map

Docusign	Formable
Create template / upload documents	`POST /v1/templates`
Template edit view (e.g. `TemplateViews:createEdit`)	`POST /v1/templates/{templateId}/edit-url`
`editUrl` on create	`editTemplateAccess.editUrl` returned from create

Auth

Docusign template APIs sit under /v2.1/accounts/{accountId}/... with an OAuth token. Formable uses the same Bearer key as signing:

curl https://api.formabledocs.com/v1/templates \
  --header "Authorization: Bearer fmbl_YOUR_API_KEY" \
  --form 'file=@./agreement.pdf' \
  --form 'filename=agreement.pdf'

See Authentication. Call these endpoints from your backend only.

Migrate the flow

1. Upload the template

curl --request POST \
  --url https://api.formabledocs.com/v1/templates \
  --header "Authorization: Bearer $TOKEN" \
  --form 'file=@./agreement.pdf' \
  --form 'filename=agreement.pdf' \
  --form 'signer_roles=[{"name":"Signer","order":0}]'

Response

{
  "templateId": "abc123xyz",
  "editTemplateAccess": {
    "editUrl": "https://app.formabledocs.com/template-setup/abc123xyz",
    "expiresAt": "2024-01-16T10:30:00.000Z"
  }
}

There is no separate OAuth account path. The organization comes from the API key. Supported uploads: PDF, DOCX, and DOC, up to 40MB. signer_roles is optional — pass it as a JSON string in multipart form data when you want named roles before opening the editor. You still assign those roles to required fields in the editor.

2. Get a fresh editor URL

When the create URL has expired, or whenever a user needs to edit again:

curl --request POST \
  --url https://api.formabledocs.com/v1/templates/abc123xyz/edit-url \
  --header "Authorization: Bearer $TOKEN"

Response

{
  "editUrl": "https://app.formabledocs.com/template-setup/abc123xyz",
  "expiresAt": "2024-01-16T10:30:00.000Z"
}

This replaces Docusign’s template edit view call. Generate just-in-time on your backend. Unknown IDs return 404; templates outside your organization return 403.

3. Embed on the client

<iframe
  src="https://app.formabledocs.com/template-setup/abc123xyz"
  width="100%"
  height="800"
  allow="fullscreen"
  style="border: none;"
></iframe>

Pass only the editUrl to the browser — never the API key. Template editing uses the same iframe pattern as embedded signing. Listen for onTemplateEditorSaved when the user finishes editing — see Embedded templates.

Tab → field mapping

Docusign tab	Formable field
SignHere / Signature	Signature
Text / FullName / Company	Text
DateSigned / Date	Date
Checkbox	Checkbox
Numerical / amount-style	Amount

If you previously set tab values on templateRoles when creating an envelope, use Formable fields: [{ fieldId, value }] at signature request time instead. Field IDs come from the editor after placement — see prefills.

Differences to plan for

Visual editor instead of Anchor tabs

Anchor strings and absolute coordinates in the create-envelope payload don’t carry over. Place fields in Formable’s editor and reference fieldIds for prefills.

Optional roles on template create

Docusign templates often define roles up front. Formable supports optional signer_roles on template create, but you still assign roles to required fields in the editor and pass matching signers[].role when creating the signature request.

API key instead of OAuth

Template create and edit-url calls use the same Bearer API key as signing — no account-scoped OAuth token.

Rebuild prefill keys

Docusign tabLabel values won’t match Formable fieldIds. After users place fields, store the new IDs and update your send payload.

Checklist

Create a Formable API key

In Settings.

Re-upload each template document

Call POST /v1/templates.

Replace template edit views

Embed editUrl from create or POST .../edit-url.

Map tab labels to fieldIds

Place fields in the editor and update prefill code.

Send with the new templateId

Continue with embedded signing migration.

Next steps

Embedded signing migration

Map envelopes and recipient views to Formable.

Embedded templates walkthrough

Full Formable template editor walkthrough.

Core concepts

How templates and signature requests fit together.

Authentication

Bearer fmbl_ API keys.

Getting Started

Walkthroughs

SDKs

Migrations

Webhooks

Docusign → Embedded templates

What you’re moving

Recommended order of work

What’s similar

What’s different

Concept map

Endpoint map

Auth

Migrate the flow

1. Upload the template

2. Get a fresh editor URL

3. Embed on the client

Tab → field mapping

Differences to plan for

Checklist

Next steps

Embedded signing migration

Embedded templates walkthrough

Core concepts

Authentication

​What you’re moving

​Recommended order of work

​What’s similar

​What’s different

​Concept map

​Endpoint map

​Auth

​Migrate the flow

​1. Upload the template

​2. Get a fresh editor URL

​3. Embed on the client

​Tab → field mapping

​Differences to plan for

​Checklist

​Next steps

Embedded signing migration

Embedded templates walkthrough

Core concepts

Authentication

What you’re moving

Recommended order of work

What’s similar

What’s different

Concept map

Endpoint map

Auth

Migrate the flow

1. Upload the template

2. Get a fresh editor URL

3. Embed on the client

Tab → field mapping

Differences to plan for

Checklist

Next steps