Integration

pdfFiller integration

pdfFiller (airSlate) edits, fills and signs PDF documents. With its API an agent can list, upload (from a URL or a stored file), rename, move, copy, fill, download and delete documents and read their fillable fields and signer roles; create LinkToFill fill requests (a public link others fill out) and read, export, download or delete the filled forms; send documents for e-signature (pdfFiller emails each recipient), follow, remind, resend or cancel signature requests, and download the signed document and its certificate; manage folders and document-event callbacks; and read the current user. Not exposed: OAuth token routes, the account-wide global callback, OAuth applications, organizations and their users, token records, custom logos, editor (constructor) and share links, page previews, zip exports, additional-document downloads and merging. Authentication is the API key from the API Settings tab of the pdfFiller developer site, sent as a Bearer token.

Connect pdfFiller How integrations work

Ask it in chat

Say what should happen.
The workflow builds itself.

When this happens, do that in pdfFiller.Built from the 44 pdfFiller tools below, on the connection you add once.

What you can do with pdfFiller

Each of these is one operation on one endpoint, available both as a workflow step and as a tool an AI agent can call on its own. Nothing bundles several operations into one action, so what a run did stays readable afterwards.

Most endpoints run on the free plan. A few, mainly the ones that publish on your behalf, need a paid plan.

Template, 8 operations

copy_templateCopy templatePOSTCopies a pdfFiller document under a new name, optionally into another folder, and returns the copy. action must be copy.
create_template_from_urlCreate template from urlPOSTCreates a pdfFiller document from a file at a public URL (PDF, DOC, DOCX, PPT or PPTX; converted to PDF) and returns it with its id. with_tags turns the text tags in the document into fillable fields.
delete_templateDelete templateDELETEDeletes a pdfFiller document.
fill_templateFill templatePOSTFills the fields of a fillable document (one built with the pdfFiller editor) with your values and returns the newly filled document. Read the field names with list_template_fields.
get_templateGet templateGETReturns one pdfFiller document: id, name, original type, processing status (RECEIVED, FINISHED, FAILED), created and updated times, whether it is fillable, and its folder.
list_templatesList templatesGETLists the documents in the pdfFiller account with id, name, original type, processing status, created and updated times, whether they are fillable, and folder. Filter by folder; paginated.
update_templateUpdate templatePUTRenames a pdfFiller document or moves it to another folder, and returns the updated document.
upload_templateUpload templatePOSTUploads a stored file (PDF, DOC, DOCX, PPT or PPTX; converted to PDF) as a new pdfFiller document and returns it with its id. with_tags turns the text tags in the document into fillable fields.

Callback, 5 operations

create_callbackCreate callbackPOSTCreates a callback: pdfFiller calls callback_url when the chosen event (fill_request.done, signature_request.done or constructor.done) happens on a document. Returns the callback.
delete_callbackDelete callbackDELETEDeletes a callback.
get_callbackGet callbackGETReturns one callback: its document, event and URL.
list_callbacksList callbacksGETLists the document callbacks: id, document, event (fill_request.done, signature_request.done, constructor.done) and the URL pdfFiller calls. Paginated.
update_callbackUpdate callbackPUTChanges the event or URL of a callback and returns it.

Fillable form, 5 operations

create_fillable_formCreate fillable formPOSTCreates a LinkToFill fill request from a document and returns its public url to share with the people who should fill it. Can prefill fields and set access, required name or email, notifications and a redirect.
delete_fillable_formDelete fillable formDELETEDeletes a LinkToFill fill request.
get_fillable_formGet fillable formGETReturns one LinkToFill fill request: public link URL, document name, access level and permission, required name or email, notification mode, redirect, options and number of filled forms.
list_fillable_formsList fillable formsGETLists LinkToFill fill requests (documents shared through a public link for others to fill) with id, document name, link URL, access, permission, notification mode, options and filled form count. Paginated.
update_fillable_formUpdate fillable formPUTChanges the settings of a LinkToFill fill request (access, permission, required name or email, downloads, redirect, message, notifications and options) and returns it.

Folder, 5 operations

create_folderCreate folderPOSTCreates a folder, optionally inside a parent folder, and returns it.
delete_folderDelete folderDELETEDeletes a folder.
get_folderGet folderGETReturns one folder: name, document and subfolder counts, and parent folder.
list_foldersList foldersGETLists the folders of the pdfFiller account with id, name, document and subfolder counts and parent folder. Paginated.
update_folderUpdate folderPUTRenames a folder and returns it.

Signature request, 5 operations

cancel_signature_requestCancel signature requestDELETECancels a signature request.
create_signature_requestCreate signature requestPOSTSends a document for e-signature: pdfFiller emails each recipient a signing request. sendtoeach has the document signed individually; sendtogroup has it signed by several recipients (envelope_name, sign_in_order and roles).
get_signature_requestGet signature requestGETReturns one signature request: document, method, status (IN_PROGRESS, DECLINE, REJECTED, COMPLETED), envelope, security level, created and signed dates, recipients with their signing status, and callbacks.
list_signature_requestsList signature requestsGETLists the signature requests (SendToSign) the account sent, with document, method, status, envelope, security level, dates, recipients and their signing status. Paginated.
resend_signature_requestResend signature requestPOSTResends a signature request: pdfFiller creates a duplicate of it and sends it to the recipients again, in the order set on the original. Returns the new request.

Filled form, 3 operations

delete_filled_formDelete filled formDELETEDeletes one filled form of a LinkToFill fill request.
get_filled_formGet filled formGETReturns one filled form of a LinkToFill fill request: filled document id, filler name and email, date, IP, attached documents and reusable copy.
list_filled_formsList filled formsGETLists the forms filled through a LinkToFill fill request: filled form id, filled document id, filler name and email, date, IP and attached documents. Paginated.

Recipient, 3 operations

add_signature_recipientsAdd signature recipientsPOSTAdds recipients to an existing signature request; each new recipient is sent the signing request email you describe. Returns the updated request.
get_signature_recipientGet signature recipientGETReturns one recipient of a signature request: email, name, signing status (NOT_SENT, DECLINE, SENT, SIGNED), order, access, email subject and text, dates, roles and attached documents.
list_signature_recipientsList signature recipientsGETLists the recipients of a signature request with email, name, signing status (NOT_SENT, DECLINE, SENT, SIGNED), order, access, dates, roles and attached documents. Paginated.

Download, 2 operations

download_filled_formDownload filled formGETDownloads one filled form of a LinkToFill fill request as a PDF file.
download_templateDownload templateGETDownloads a pdfFiller document as a PDF file. Call it once get_template reports status FINISHED: while the file is still being prepared pdfFiller answers 211 (not ready) instead of the file.

Certificate, 1 operation

download_signature_certificateDownload signature certificateGETDownloads the signature certificate of a signature request as a PDF file.

Export, 1 operation

export_filled_formExport filled formGETExports the data entered in one filled form: filler name and email, date and time, page count, email status and, per page, each fillable field with its content.

Field, 1 operation

list_template_fieldsList template fieldsGETLists the fillable fields of a document with type, name, label, required flag, initial and current value, list choices, radio group and format. Use the names as keys of fill_template fillable_fields.

Me, 1 operation

get_current_userGet current userGETReturns the pdfFiller user the API key belongs to: id, email and avatar.

Original document, 1 operation

download_original_documentDownload original documentGETDownloads the original file a pdfFiller document was created from.

Remind, 1 operation

remind_signature_recipientRemind signature recipientPUTEmails a reminder about the signature request to one recipient.

Role, 1 operation

list_template_rolesList template rolesGETLists the signer roles defined on a document (id, role name, signing order); a role id is what a sendtogroup recipient of create_signature_request takes as role.

Signed document, 1 operation

download_signed_documentDownload signed documentGETDownloads the signed document of a signature request as a PDF file.

Use pdfFiller from Claude Code, Cursor or Codex

Connect pdfFiller in LiveContext, create an API key in Settings, then add the LiveContext MCP server to your client. Its pdfFiller operations become tools the client can call, next to every other integration you connected.

Claude Code

claude mcp add --transport http livecontext https://livecontext.ai/mcp --header "X-API-Key: YOUR_API_KEY"

Codex (~/.codex/config.toml)

[mcp_servers.livecontext]
url = "https://livecontext.ai/mcp"

[mcp_servers.livecontext.http_headers]
"X-API-Key" = "YOUR_API_KEY"

Cursor, Claude Desktop and other JSON configs

{
  "mcpServers": {
    "livecontext": {
      "type": "http",
      "url": "https://livecontext.ai/mcp",
      "headers": {
        "X-API-Key": "YOUR_API_KEY"
      }
    }
  }
}

Set up the MCP server step by step

How to connect pdfFiller

Create your workspace
Sign up free. Nothing to install.
Connect pdfFiller once
Add your pdfFiller connection in Settings. Every tool from this integration reuses it, and secrets are encrypted at rest and visible only to you.
Describe the job in chat
The workflow builds itself in front of you and picks the endpoints it needs. Drag the steps yourself on the canvas whenever you would rather be explicit.