Commercial workflow page
Turn a reviewed saved template into a hosted JSON-to-PDF endpoint with schema downloads, key rotation, rate limits, and audit activity.
E-sign pipeline
Single-signer, sequential multi-signer, parallel multi-signer, Fill By Link → sign, group fill → multi-sign, and API Fill → sign — walked end to end across HR onboarding, healthcare intake, real estate, legal, insurance ACORD, and immigration USCIS workflows.
Use this video as the canonical reference for DullyPDF e-signatures: pick the signing workflow your team actually runs, then match it to the industry-specific packet you already send out today.
Some teams still want an operator in the loop, which is exactly what Search & Fill is for. But other teams already have the record data in another system and need a server-to-server way to turn that data into a filled PDF. In that case a JSON-to-PDF API is the better product shape because the external system can call one endpoint without recreating the template logic itself.
That API only works well if it is tied to a reviewed template snapshot. Otherwise the caller is sending data into a moving target. DullyPDF treats API Fill as a published snapshot of a saved template so the schema, field rules, and output expectations stay stable until the owner intentionally republishes or rotates the endpoint.
Search & Fill is browser-local: an operator loads data, searches rows, picks the record, and validates the result in the workspace. API Fill is a hosted runtime. The caller sends structured JSON, authenticates with the endpoint key, and receives a PDF back from the backend. Those are different trust boundaries and should not be blurred together.
That distinction matters operationally too. Hosted API requests need their own rate limits, request caps, and audit activity. Browser-local Search & Fill does not. Keeping those boundaries explicit makes the product easier to reason about and easier to secure later.
An API caller cannot rely on informal UI hints. The template has to define exactly how text fields, checkbox rules, radio groups, and transforms behave when the JSON payload arrives. That is why DullyPDF exposes radio group expectations and deterministic fill rules as part of the frozen template schema instead of leaving those behaviors implicit.
The result is a tighter contract between the saved template and the system calling it. When the template is updated, the endpoint and schema can be rotated intentionally rather than silently drifting under production traffic.
This page is for the product decision: should a reviewed template become a hosted endpoint at all? Search & Fill remains the better fit when an operator still needs to search records in the browser and review each output manually. The API docs become more useful only after the hosted-endpoint decision is made and the team needs exact publication, schema, and key-management steps.
That separation keeps the query intent cleaner. Commercial API terms should land on the hosted-endpoint route. Runtime setup questions should land on the docs. Operator-driven filling should land on the Search & Fill route. The more clearly those pages are separated, the less likely they are to compete with each other.
Need deeper technical details about pdf fill api? Use the Rename + Mapping docs and Search & Fill docs to validate exact behavior.
It is a template-scoped JSON-to-PDF endpoint published from a saved DullyPDF template, with its own schema, key, rate limits, and audit activity.
Search and Fill keeps chosen row data local in the browser, while API Fill is a hosted backend runtime for other systems that need a JSON-to-PDF endpoint.
Yes. The published schema includes deterministic fill rules, including checkbox rules, radio group expectations, and text transforms from the frozen saved-template snapshot.
These walkthroughs and comparison posts cover the same workflow cluster from an operator point of view, which helps you move from a route summary into a more specific implementation path.
Use these docs pages to verify the exact DullyPDF behavior behind pdf fill api before you ship it as a repeat workflow.
These adjacent workflow pages cover nearby search intents teams compare while evaluating pdf fill api.
