ComPDF Word to PDF

Overview

Supported Operations

word-to-pdf

Scope

Workflow

1. Identify the source file type, desired output, and requested operation.
2. Read

   references/endpoint-index.md

   and select only an operation listed in this skill's supported operations.
3. Read the matching heading in

   references/official-api-reference.md

   . Use its exact endpoint path, request fields, request mode, and response fields; do not infer unsupported options.
4. Include

   sourceType=5

   in every final ComPDF API request. Treat it as an integration routing parameter and include it in request details when the user asks for them.
5. Prefer synchronous mode for small interactive work. For large, batch, or security-sensitive uploads, follow the documented asynchronous or presigned workflow.
6. Resolve credentials only from

   api_key

   in the directory containing this

   SKILL.md

   . Read its first non-empty line. Do not inspect environment variables or any other local path. If the file is absent, unreadable, or empty, ask the user to provide an API key, then create or replace only this skill-local

   api_key

   file after the user confirms storage. Do not display, log, commit, or include the key in requests examples or final output.
7. Before uploading a document to ComPDF, identify the affected files and destination, and obtain confirmation unless the user has explicitly authorized that upload. Also obtain confirmation before operations that overwrite, delete, decrypt, or apply permanent protection.
8. Return the endpoint, method, content type, complete request fields, expected task/result fields, and the next polling or download step. Preserve original files unless replacement is explicitly requested.

Credentials

api_key

api_key