Skip to navigation

Move from Paperwork signing

Adopt RakeSign for new integrations while existing signing runs continue.
View as Markdown

Use /v1/signing for new product integrations. It exposes RakeSign documents, templates, consent, webhooks, and administration through one product surface.

POST /v1/sign remains available for existing Paperwork callers. Its request body, response shape, run URLs, retention rules, and signing behavior remain compatible. Existing runs continue through their current endpoints.

Compare the workflows

Existing Paperwork workflowRakeSign workflow
Organization API keyScoped key for one managed team
POST /v1/sign with a file and signersCreate a document, add a PDF, then send
GET /v1/runs/:idGET /v1/signing/documents/:id
Run envelope and audit routesDocument progress, PDF, and audit routes
Paperwork webhook subscriptionsTeam-scoped RakeSign event subscriptions
Legacy template delegation scopeConsent for a saved RakeSign template revision
Run-based integration recordsShared RakeSign document records with integration origin

Both paths use the same signing engine. They retain different resource contracts so existing integrations can continue.

Migrate new work

  1. Create a RakeSign integration key for the target team.
  2. Select only the required permissions.
  3. Create or save templates in that team when the integration needs reusable documents.
  4. Implement the document workflow.
  5. Register RakeSign webhooks and verify their payloads.
  6. Route new requests to RakeSign after your integration checks pass.

Keep polling existing Paperwork runs through their original URLs until they finish. Do not resubmit an in-flight document to RakeSign as a migration step. That would create a separate signing request.

Keep existing records

The migration does not import old runs into RakeSign automatically. Existing Paperwork runs do not gain team visibility or RakeSign document IDs. Their retention and access rules remain unchanged.

RakeSign keys cannot call the legacy /v1/sign route. Keep the existing credential for legacy work until that work finishes.

Recreate delegation scope

Create a saved RakeSign template and request consent for its current revision. Do not copy an old consent status into a new grant. The signer must accept the new revision-bound request.

Read standing delegation before enabling delegated sends.