How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

PDFfiller Signature Requests API

Manage eSignature requests and workflows

PDFfiller Signature Requests API is one of 11 APIs that PDFfiller publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Signature Requests. The published artifact set on APIs.io includes an OpenAPI specification and API documentation.

This API exposes 15 operations across 12 paths, and defines 7 schemas. It is described by OpenAPI 3.0.3, at version 2.0.

Requests are made against a single base URL, https://api.pdffiller.com/v2.

15 operations 12 paths 7 schemas 1 DELETE12 GET1 POST1 PUT

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.0.3
API Version
2.0
Base URL
https://api.pdffiller.com/v2/
Authentication
OAuth 2.0
Resource Areas
1

Authentication & Security 1

PDFfiller Signature Requests API declares 1 security scheme for authenticating requests. It supports OAuth 2.0 (oauth2) using the password and clientCredentials flows, exposing 2 scopes. By default, every request must be authenticated.

Paths & Operations 15

Across 12 paths, the API surfaces 15 operations — 1 DELETE, 12 GET, 1 POST, 1 PUT. Each is listed below with its method, path, parameters, and response codes.

Signature Requests 15

Manage eSignature requests and workflows

GET
/signature_requests/inbox
List inbox signature requests
listSignatureRequestsInbox 7 params → 200401
GET
/signature_requests/inbox/download
Download inbox signature requests
downloadInboxSignatureRequests 6 params → 200
GET
/signature_requests
List all signature requests
listSignatureRequests 6 params → 200401
POST
/signature_requests
Create a signature request
createSignatureRequest body → 201401
GET
/signature_requests/{signature_request_id}
Get signature request by ID
getSignatureRequest 1 param → 200404
DELETE
/signature_requests/{signature_request_id}
Delete a signature request
deleteSignatureRequest 1 param → 204404
GET
/signature_requests/{signature_request_id}/certificate
Get signature certificate
getSignatureRequestCertificate 1 param → 200404
GET
/signature_requests/{signature_request_id}/signed_document
Download signed document
downloadSignedDocument 1 param → 200404
GET
/signature_requests/{signature_request_id}/recipients
List signature request recipients
listSignatureRequestRecipients 1 param → 200404
GET
/signature_requests/{signature_request_id}/recipients/{recipient_id}
Get signature request recipient
getSignatureRequestRecipient 2 params → 200404
PUT
/signature_requests/{signature_request_id}/recipients/{recipient_id}
Send reminder to recipient
remindSignatureRequestRecipient 2 params → 200404
GET
/signature_requests/{signature_request_id}/recipients/{recipient_id}/additional_documents
List recipient additional documents
listRecipientAdditionalDocuments 2 params → 200404
GET
/signature_requests/{signature_request_id}/recipients/{recipient_id}/additional_documents/download
Download all recipient additional documents
downloadRecipientAdditionalDocuments 2 params → 200
GET
/signature_requests/{signature_request_id}/recipients/{recipient_id}/additional_documents/{additional_document_id}
Get recipient additional document
getRecipientAdditionalDocument 3 params → 200
GET
/signature_requests/{signature_request_id}/recipients/{recipient_id}/additional_documents/{additional_document_id}/download
Download recipient additional document
downloadRecipientAdditionalDocument 3 params → 200

Schemas 7

The contract defines 7 schemas that model the data the API accepts and returns. The most detailed are SignatureRequest (9 properties), SignatureRequestInput (8 properties), Recipient (6 properties), RecipientInput (6 properties). Each schema is shown below with its type and property counts.

SignatureRequest
object
9 properties
RecipientInput
object
6 properties 1 required
Error
object
3 properties
SignatureRequestList
object
4 properties
SignatureRequestInput
object
8 properties 3 required
Recipient
object
6 properties
AdditionalDocument
object
5 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

pdffiller-signature-requests-api-openapi.yml Raw ↑

Other APIs PDFfiller publishes across the network.

PDFfiller Applications API
PDFfiller Auth API
PDFfiller Callbacks API
PDFfiller Custom Logos API
PDFfiller Fillable Forms API
PDFfiller Folders API
PDFfiller Templates API
PDFfiller Tokens API
PDFfiller Tools API
PDFfiller Users API
Where this information came from

This is an independent, third-party profile of PDFfiller Signature Requests API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.