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 Callbacks API

Manage webhook callbacks for document events

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

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

This API exposes 8 operations across 3 paths, and defines 4 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.

8 operations 3 paths 4 schemas 2 DELETE3 GET1 POST2 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 Callbacks 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 8

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

Callbacks 8

Manage webhook callbacks for document events

GET
/callbacks
List all callbacks
listCallbacks 4 params → 200401
POST
/callbacks
Create a callback
createCallback body → 201401
GET
/callbacks/{callback_id}
Get callback by ID
getCallback 1 param → 200404
PUT
/callbacks/{callback_id}
Update a callback
updateCallback 1 param body → 200404
DELETE
/callbacks/{callback_id}
Delete a callback
deleteCallback 1 param → 204404
GET
/callbacks/global
Get global callback
getGlobalCallback → 200401
PUT
/callbacks/global
Update global callback
updateGlobalCallback body → 200
DELETE
/callbacks/global
Delete global callback
deleteGlobalCallback → 204

Schemas 4

The contract defines 4 schemas that model the data the API accepts and returns. The most detailed are Callback (5 properties), Error (3 properties), CallbackInput (3 properties), CallbackList (2 properties). Each schema is shown below with its type and property counts.

Callback
object
5 properties
CallbackInput
object
3 properties 1 required
Error
object
3 properties
CallbackList
object
2 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

pdffiller-callbacks-api-openapi.yml Raw ↑

Other APIs PDFfiller publishes across the network.

PDFfiller Applications API
PDFfiller Auth API
PDFfiller Custom Logos API
PDFfiller Fillable Forms API
PDFfiller Folders API
PDFfiller Signature Requests 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 Callbacks 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.