Skip to main content
This guide walks you through the complete signing flow: uploading a PDF, sending it for signature, and downloading the completed document. By the end, you will have a working integration you can build on.

Prerequisites

  • A SpitShake account (sign up free)
  • A PDF document to send for signing
  • An API token (generated in the next step)

Step 1: Get your API token

Navigate to Settings > API in your SpitShake dashboard and click Create Token. Give it a descriptive name (e.g., “Quickstart”) and select the scopes you need. For this tutorial, enable templates:write and submissions:write. Copy the token — you will not be able to see it again.
Keep your API token secret. Do not commit it to version control or expose it in client-side code.

Step 2: Create a template from PDF

Upload a PDF and SpitShake will create a template with a default submitter role. You can optionally specify fields, but for this quickstart we will keep it simple and let the signer fill in all fields manually.
Response:
Save the id from the response. You will use it in the next step to create a submission.

Step 3: Create a submission

Now send the template for signing. Provide the submitter’s email and name, mapped to the submitter role from the template.
Response:
Jane will receive an email with a link to sign the document. You can also construct the signing URL directly: https://spitshake.io/s/r7t2q9v4.

Step 4: Check submission status

Poll the submission to see when it has been completed, or set up webhooks for real-time notifications.
Response when completed:
Instead of polling, use webhooks to receive a submission.completed event in real time.

Step 5: Download the signed document

Once the submission status is completed, download the final signed PDF with all fields filled and signatures applied.
The response is a binary PDF file with Content-Disposition: attachment headers.

What’s next?

You have successfully sent a document for signing and downloaded the completed result. Here are some next steps to explore:

Templates

Define field schemas, submitter roles, and create templates from DOCX or HTML.

Submissions

Pre-fill fields, use quick sign modes, create drafts, and bulk-send documents.

Submitters

Track individual signer status, resend invitations, and map external IDs.

Webhooks

Get real-time notifications instead of polling for submission status changes.

Embedding

Embed the signing experience directly in your application.

Authentication

Learn about API token scopes, JWT tokens, and security best practices.