Availability: Enterprise*

* Additional volume charge will be applied for document generation via production API.

These instructions assume:

If you want to include PandaDoc native elements such as signature or text fields in your PDF-derived document, you’ll need to use either the PDF native form fields structure or add manual field tags to the PDF.

An example of form fields is available here.

An example of field tags is available here.

You can read more about the structure and respective benefits of form fields versus field tags in the Create document from PDF documentation. If you choose to use form fields, make sure you set "parse_form_fields": true; otherwise set "parse_form_fields": false.

Once you’ve finalized your PDF, you’re ready for the next step.

You’ll need to post your PDF to a publicly accessible URL. For example, if you’re using an S3 bucket on AWS, you’ll need to set the GetObject to “allow” for *. The PDF must be fully uploaded and accessible before you post it to PandaDoc.

To inform PandaDoc to ingest and parse your PDF, add:

POST https://api.pandadoc.com/public/v1/documents/

Be sure to include content type application/JSON and a JSON block to identify the document.

The response will contain the document ID as the element “id”:

See Listening for changes in document status. If you’re actively polling your document, the ID is “id” from the previous step.

Once you’ve determined that the document has entered “document.draft” status, you can send it by adding the following ({id} is the document ID from above):

POST https://api.pandadoc.com/public/v1/documents/{id}/send

You can also include these optional parameters in your POST to set a subject line and body text:

Don’t set the “silent” parameter to “true” unless you don’t want an email to go out with the document link. For more information about why you might want to send silently, see “Create a document and share it in real time.”