Skip to main content
POST
cURL
Creates a signature request for generated title documents. You can send an explicit body with signers and documents_to_sign, or omit the body entirely to let the API build the request from the title entry. Auto-build requires signer contact_email values to already be present on the entry, usually via a prior PATCH /title/{id}. redirect_url belongs in the request body, not the query string.

Signing URLs in the response

For Notarize/Proof-based organizations, the response includes per-signer signing URLs at signers[].transaction_access_url. Each signer receives their own unique link to access the signing session.
The top-level transaction_access_url on the SignatureRequest object is not populated on the initial create response — it is only set after an explicit activate action on a DRAFT request. Always read signing URLs from signers[].transaction_access_url. DocuSign-based requests do not include transaction_access_url — signing links are delivered directly to signers via email by DocuSign. Internal signature actions for managing existing requests are not part of the partner-facing API surface.

Authorizations

Authorization
string
header
required

API key or Clerk JWT supplied as Authorization: Bearer

Path Parameters

id
string
required

Unique identifier of the title entry

Body

application/json

Customization options for the signature request (e.g., in cases where you don't want to collect signatures from all titled owners).

signers
object[]

List of specific people who should sign the documents. Each signer must include contact_email. If the body is omitted entirely, the API attempts to build signers from current owners/borrowers already stored on the entry.

Minimum array length: 1
documents_to_sign
object[]

List of specific documents to be signed.

Minimum array length: 1
redirect_url

Optional redirect URL or redirect descriptor used by the signature provider after signing.

requester_email
string

Additional notification email for signature completion

instructions
string

Special instructions for the signer

Response

Signature request created successfully

transaction_access_url
string<uri>
read-only

Top-level transaction URL. Only populated after an explicit activate action on a DRAFT Notarize/Proof request. For the initial create response, look at each signer's transaction_access_url instead.

redirect_url
object
requester_email
string

Additional notification email for signature completion

id
string

Provider-specific ID (NTRZ::id for Notarize, DSGN::id for DocuSign, DMNS::id for Documenso, PNDC::id for Pandadoc)

type
enum<string>

Type of signature required

Available options:
WET_SIGN,
WET_NOTARY,
RON,
E_SIGN,
NONE
status
enum<string>

Current status of the signature request

Available options:
DRAFT,
SENT,
OPENED,
COMPLETED,
FAILED,
EXPIRED
documents_to_sign
object[]
created_at
string

When the request was created

updated_at
string

Last status update

signers
object[]

Signers on this request. In the response from POST /title/{id}/sign, each signer object includes a transaction_access_url field with the per-signer signing link (Notarize/Proof provider only).

sign_cert
string

S3 path to signing certification

collected_dlid
string

S3 path to collected driver license ID

full_export
string

S3 path to full export consisting of sign cert, collected_dlid, and documents_to_sign

physical_tracking
object
instructions
string

Any special instructions for the signer

metadata
object

Additional provider-specific metadata