pandoc-server [options]
pandoc-server is a web server that can perform pandoc conversions. It can be used either as a running server or as a CGI program.
To use pandoc-server as a CGI program, rename it (or symlink it) as pandoc-server.cgi. (Note: if you symlink it, you may need to adjust your webserver’s configuration in order to allow it to follow symlinks for the CGI script.)
All pandoc functions are run in the PandocPure monad, which ensures that they can do no I/O operations on the server. This should provide a high degree of security. This security does, however, impose certain limitations:
PDFs cannot be produced.
Filters are not supported.
Resources cannot be fetched via HTTP.
Any images, include files, or other resources needed for the document conversion must be explicitly included in the request, via the files field (see below under API).
HTTP port on which to run the server. Default: 3030.
Timeout in seconds, after which a conversion is killed. Default: 2.
When pandoc-server is run as a CGI program, this option can be set via the PANDOC_SERVER_TIMEOUT environment variable.
Print this help.
Print version.
The root (/) endpoint accepts only POST requests. It returns a converted document in one of the following formats, depending on Accept headers:
text/plain
application/json
application/octet-stream
If the result is a binary format (e.g., epub or docx) and the content is returned as plain text or JSON, the binary will be base64 encoded.
The body of the POST request should be a JSON object, with the following fields. Only the text field is required; all of the others can be omitted for default values. When there are several string alternatives, the first one given is the default.
The document to be converted. Note: if the from format is binary (e.g., epub or docx), then text should be a base64 encoding of the document.
The input format, possibly with extensions, just as it is specified on the pandoc command line.
The output format, possibly with extensions, just as it is specified on the pandoc command line.
Increase or decrease the level of all headings.
List of classes to be applied to indented Markdown code blocks.
Extension to be applied to image sources that lack extensions (e.g. ".jpg").
String-valued metadata.
Tab stop (spaces per tab).
Specifies what to do with insertions, deletions, and comments produced by the MS Word “Track Changes” feature. Only affects docx input.
List of strings to be regarded as abbreviations when parsing Markdown. See --abbreviations in pandoc(1) for details.
If true, causes a standalone document to be produced, using the default template or the custom template specified using template. If false, a fragment will be produced.
String contents of a document template (see Templates in pandoc(1) for the format).
Variables to be interpolated in the template. (See Templates in pandoc(1).)
Dots-per-inch to use for conversions between pixels and other measurements (for image sizes).
Text wrapping option: either "auto" (automatic hard-wrapping to fit within a column width), "preserve" (insert newlines where they are present in the source), or "none" (don’t insert any unnecessary newlines at all).
Column width (affects text wrapping and calculation of table column widths in plain text formats)
Include a table of contents (in supported formats).
Depth of sections to include in the table of contents.
Causes HTML comments to be stripped in Markdown or Textile source, instead of being passed through to the output format.
Specify the style to use for syntax highlighting of code. Standard styles are "pygments" (the default), "kate", "monochrome", "breezeDark", "espresso", "zenburn", "haddock", and "tango". Alternatively, the path of a .theme with a KDE syntax theme may be used (in this case, the relevant file contents must also be included in files, see below).
Embed images, scripts, styles and other resources in an HTML document using data URIs. Note that this will not work unless the contents of all external resources are included under files.
Use <q> elements in HTML instead of literal quotation marks.
Use entities and escapes when possible to avoid non-ASCII characters in the output.
Create reference links rather than inline links in Markdown output.
Determines whether link references and footnotes are placed at the end of the document, the end of the section, or the end of the block (e.g. paragraph), in certain formats. (See pandoc(1) under --reference-location.)
Use Setext (underlined) headings instead of ATX (#-prefixed) in Markdown output.
Determines how top-level headings are interpreted in LaTeX, ConTeXt, DocBook, and TEI. The "default" value tries to choose the best interpretation based on heuristics.
Automatically number sections (in supported formats).
Offsets to be added to each component of the section number. For example, [1] will cause the first section to be numbered “2” and the first subsection “2.1”; [0,1] will cause the first section to be numbered “1” and the first subsection “1.2.”
Determines how math is represented in HTML.
Use the listings package to format code in LaTeX output.
If true, lists appear incrementally by default in slide shows.
Heading level that deterimes slide divisions in slide shows. The default is to pick the highest heading level under which there is body text.
Arrange the document into a hierarchy of nested sections based on the headings.
Determines how email addresses are obfuscated in HTML.
Prefix to be added to all automatically-generated identifiers.
Prefix to be added to the title in the HTML header.
Reference doc to use in creating docx or odt or pptx. See pandoc(1) under --reference-doc for details. The contents of the file must be included under files.
Cover image for EPUB. The contents of the file must be included under files.
Path of file containing Dublin core XML elements to be used for EPUB metadata. The contents of the file must be included under files.
Heading level at which chapter splitting occurs in EPUBs.
Name of content subdirectory in the EPUB container.
Fonts to include in the EPUB. The fonts themselves must be included in files (see below).
Determines how ipynb output cells are treated. all means that all of the data formats included in the original are preserved. none means that the contents of data cells are omitted. best causes pandoc to try to pick the richest data block in each output cell that is compatible with the output format.
Causes citations to be processed using citeproc. See Citations in pandoc(1) for details.
Files containing bibliographic data. The contents of the files must be included in files.
CSL style file. The contents of the file must be included in files.
Determines how citations are formatted in LaTeX output.
Any files needed for the conversion, including images referred to in the document source, should be included here. Binary data must be base64-encoded. Textual data may be left as it is, unless it is also valid base 64 data, in which case it will be interpreted that way.
The /batch endpoint behaves like the root endpoint, except for these two points:
It accepts a JSON array, each element of which is a JSON object like the one expected by the root endpoint.
It returns a JSON array of results. (It will not return plain text or octet-stream, like the root endpoint.)
This endpoint can be used to convert a sequence of small snippets in one request.
The /version endpoint accepts a GET request and returns the pandoc version as a plain or JSON-encoded string, depending on Accept headers.
The /babelmark endpoint accepts a GET request with the following query parameters:
text (required string)
from (optional string, default is "markdown")
to (optional string, default is "html")
standalone (optional boolean, default is false)
It returns a JSON object with fields html and version. This endpoint is designed to support the Babelmarkhttps://babelmark.github.io website.
Copyright 2022 John MacFarlane (jgm@berkeley.edu). Released under the GPL, version 2 or greater. This software carries no warranty of any kind. (See COPYRIGHT for full copyright and warranty notices.)