Start from the approved document
Create templates, fill their values and generate immutable PDFs when a recipient signing workflow is not required.
Connect SignThat to your CRM, ERP, HR platform or product. When a deal, hire or order is ready, your system can create the agreement, invite recipients and receive the signed result in the same familiar process.
Use the API when a signature is the natural next step. Your source system can prepare the document, identify the recipients, trigger delivery and respond as the agreement moves toward completion.
Create templates, fill their values and generate immutable PDFs when a recipient signing workflow is not required.
Create a standard agreement, add one or more recipients and send individual secure links from the business event that brings it to life.
Query the current state or receive signed webhook events so the source system can respond as progress changes or signing completes.
Attach external IDs and metadata so SignThat records map neatly to your own entities. Idempotency keys keep supported creation and sending operations safe when a network request needs to be retried.
curl -X POST https://api.signthat.app/v1/contracts \
-H 'Authorization: Bearer st_live_…' \
-H 'Idempotency-Key: order-7821' \
-d '{
"template_id": 42,
"external_id": "order_7821",
"recipients": [{
"name": "Jane Smith",
"email": "jane@example.com"
}]
}'Participant encryption keys never leave their browsers, so API-created agreements use standard secure storage. When zero-knowledge content handling is needed, start the protected agreement in the web application instead.
Compare security workflows →Create the order form while the deal has momentum, then return signed completion to the deal record.
Prepare the recurring document, send the right details and retain its final status with the person record.
Generate a final PDF or start a recipient agreement from the event that makes the document necessary.
Bring the agreement and its completed result into the system your team already knows.