Add email, PostScript, and refry endpoint examples - #133
Merged
datalogics-jacksonm merged 5 commits intoSep 2, 2026
Merged
Conversation
- Add JSON and multipart Email-to-PDF examples for C#, Java, JavaScript, PHP, Python, and cURL. - Show both resource-ID and direct-upload request patterns so developers can choose the approach that fits their workflow. Assisted-by: Codex
- Add JSON and multipart PDF-to-PostScript examples for C#, Java, JavaScript, PHP, Python, and cURL. - Demonstrate Level 3 output and commonly used page, scaling, and annotation settings. Assisted-by: Codex
- Add JSON and multipart PostScript-to-PDF examples for C#, Java, JavaScript, PHP, Python, and cURL. - Include a Distiller-compatible .joboptions profile in each workflow to demonstrate supported conversion settings. Assisted-by: Codex
- Add PDF-to-PostScript-to-PDF examples for C#, Java, JavaScript, PHP, Python, and cURL. - Document the intentionally lossy roundtrip and its print and prepress use cases. Assisted-by: Codex
- Expose Email-to-PDF, PostScript conversion, and refry commands in the .NET sample dispatcher and its usage help. Assisted-by: Codex
datalogics-jacksonm
approved these changes
Sep 2, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Why this change
Developers need practical, language-specific examples for converting email and
PostScript content to PDF, generating PostScript from PDF, and combining the
two operations into a PDF refrying workflow. These examples make the supported
request patterns and conversion options easier to adopt without changing the
API itself.
What changed
This adds JSON and multipart endpoint examples for Email-to-PDF,
PDF-to-PostScript, and PostScript-to-PDF in C#, Java, JavaScript, PHP, Python,
and cURL. The PostScript-to-PDF examples include an optional Adobe
Distiller-compatible
.joboptionsprofile. A complex workflow example in eachlanguage demonstrates the PDF -> PostScript -> PDF roundtrip and downloads the
final PDF.
The .NET dispatcher and usage help expose the new .NET examples alongside the
existing sample commands.
Why not split further: the feature commits are organized by conversion
capability, and each language needs a corresponding example set so developers
can find equivalent request patterns in their preferred language.
Behavior changes
The repository gains new opt-in examples only; existing samples and API
behavior are unchanged. The refry examples explain that the roundtrip is
intentionally lossy and may remove PDF-specific features such as tags, forms,
layers, annotations, transparency, metadata, and editability.
Validation
Validated all 42 new examples against the production API: JSON and multipart
Email-to-PDF, PDF-to-PostScript, and PostScript-to-PDF calls in all six
languages, plus each language's refry workflow. The six generated refry PDFs
passed
qpdf --check.Also verified the .NET project builds successfully and performed syntax or
package validation for the remaining language samples.
Risks and follow-ups
These are illustrative samples and use placeholder API keys and local file
paths that developers replace for their own environment. Refrying should be
used only when a workflow accepts its intentionally lossy conversion model.