Formapi DocSpring API

Name: DocSpring API
Brand: DocSpring API
Availability: InStock

✓ Official Vendor SpecProductivityForms Surveysbasic40 EndpointsREST

For Agents

Generate filled PDFs from templates, collect e-signatures via data requests, and merge multiple submissions into combined documents. Authentication is HTTP Basic with an API token ID and secret.

Install Jentic One Beta

Connect the DocSpring API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the DocSpring API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.

Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.

Step 1: Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fformapi.io%2Fdocspring" | sh

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fformapi.io%2Fdocspring" | sh
jentic register       # connects your agent to your Jentic One instance

Jentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.

Capabilities

What an agent can do with DocSpring API.

Generate filled PDFs by submitting JSON data against a versioned template

Combine multiple submissions into a single merged PDF via combined_submissions

Collect signatures and structured input from end users through data_requests with tokenised links

GET STARTED

Start building with DocSpring API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use DocSpring API for, with concrete tasks.

★ Automated Contract Generation

Fill PDF contract templates with customer data from a CRM and return a signed, finalised document. DocSpring handles field mapping, conditional logic, and version control so the same template can be reused across hundreds of contracts. Submissions complete in seconds and the API returns a permanent download URL for the generated PDF.

POST /submissions with template_id and a data payload of customer name, address, and contract value, then poll the returned submission for state=processed and download the file_url

E-Signature Collection

Send a data request link to a client, collect their input and signature, then receive the completed PDF back. DocSpring generates a tokenised URL per recipient, tracks events like opened and signed, and finalises the submission once all required fields are completed. Useful for onboarding flows that need legally formatted PDFs.

Create a data_request for template_id tpl_123 with the recipient email, fetch the resulting tokens, and email the signing URL to the client

Batch PDF Reporting

Generate hundreds of personalised PDFs in one API call by submitting a batch. DocSpring processes submissions in parallel and exposes a single batch ID that resolves to the merged combined_submission. Common for monthly statements, invoices, and certificate runs where each output is structurally identical but data-specific.

POST /submissions/batches with an array of 200 submissions, each carrying a customer_id and statement payload, then download the batch zip when state=processed

AI Agent Document Workflow

An AI agent fills a tax form template by reading values from a user's uploaded receipts, submits it through DocSpring via Jentic, and returns the finalised PDF link in chat. The agent never handles the API token directly, calls a single mcp tool, and gets a typed response that includes the download URL.

Search Jentic for 'generate a filled PDF', load the DocSpring create-submission schema, execute with template_id and the parsed receipt fields, and return the download URL

Key Endpoints

40 endpoints — docspring is a pdf generation and electronic signature service that lets developers fill out, sign, and merge pdf templates programmatically.

METHOD

PATH

DESCRIPTION

POST

/submissions

Generate a filled PDF from a template

POST

/submissions/batches

Create a batch of submissions in one call

POST

/combined_submissions

Merge multiple submissions into one PDF

GET

/templates/{template_id}/schema

Retrieve the field schema for a template

POST

/data_requests/{data_request_id}/tokens

Generate a tokenised signing URL for a recipient

POST

/templates/{template_id}/publish_version

Publish a new version of a template

POST

/submissions

Generate a filled PDF from a template

POST

/submissions/batches

Create a batch of submissions in one call

POST

/combined_submissions

Merge multiple submissions into one PDF

GET

/templates/{template_id}/schema

Retrieve the field schema for a template

POST

/data_requests/{data_request_id}/tokens

Generate a tokenised signing URL for a recipient

Why Jentic?

What agents get from Jentic-routed access to this vendor.

Setup

Wiring the DocSpring API by hand means encoding your API Token ID and Secret into HTTP Basic auth and building your own retry and error handling around its submission and template endpoints. Through Jentic you install once, import DocSpring from the API Directory, store the credentials once, and your agent calls it.

Permission scoping

DocSpring puts the template id in the URL path (/templates/{template_id}/...), so a rule can pin your agent to one template: it can read that template's schema and create submissions from it. You choose the operations it may call, so publishing a new template version is not included unless you add it.

Credential isolation

Your DocSpring API Token ID and Secret are stored once, encrypted, by your own Jentic One instance and injected at execution time. They never enter the agent's prompt, logs, or context.

Intent-based discovery

Agents search Jentic by intent such as 'generate a filled PDF' or 'collect a signature', and Jentic returns the matching DocSpring operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

FAQs

Specific to using DocSpring API through Jentic.

What authentication does the DocSpring API use?

DocSpring uses HTTP Basic authentication with the API Token ID as the username and the API Token Secret as the password. Through Jentic, these credentials are stored encrypted in the vault and never enter the agent's context - the agent receives a scoped execution token instead.

Can I generate filled PDFs from a template with the DocSpring API?

Yes. POST to /submissions with a template_id and a data object whose keys match the template's field schema. The endpoint returns a submission resource that resolves to a downloadable PDF once state=processed.

What are the rate limits for the DocSpring API?

DocSpring does not publish hard rate limits in its OpenAPI spec; the documented production limit is around 50 requests per second per account, with higher quotas available on request. Batch submissions count as a single request regardless of the number of PDFs generated.

How do I collect a signature with the DocSpring API through Jentic?

Use Jentic search query 'collect a signature on a PDF', load the DocSpring data_requests schema, and execute POST /data_requests/{data_request_id}/tokens to mint a tokenised URL for each signer. Email the URL to the recipient and poll the data_request for the signed event.

Is the DocSpring API free?

DocSpring offers a free tier with a small monthly submission allowance and paid plans that scale by submissions per month. Pricing details and current limits are published at docspring.com/pricing.

How do I generate multiple PDFs at once with the DocSpring API?

POST to /submissions/batches with an array of submissions. Each item includes its own template_id and data payload, and the batch resolves to a combined PDF or per-submission downloads. This is the recommended path for monthly statement and invoice runs.

Can I limit what my agent is allowed to do with the DocSpring API?

Yes. Because you run Jentic One yourself, your own rules decide which DocSpring operations and credentials the agent may use. Since the template id sits in the URL path, such as /templates/{template_id}/schema and /submissions, you can pin the agent to a single template so it only reads that template's schema and creates submissions from it. Operations you leave out stay off limits, so publishing a new template version via /templates/{template_id}/publish_version is not available unless you explicitly allow it.

Formapi DocSpring API

Connect the DocSpring API to your agent

Capabilities

Start building with DocSpring API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs