> ## Documentation Index
> Fetch the complete documentation index at: https://docs.blinkpdf.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Blink PDF: Markdown to PDF API 😘

> Convert Markdown to professional, accessible PDFs via a single REST endpoint. No Chromium; your Markdown input is never persisted.

Blink PDF is a high-performance REST API that converts Markdown into polished, production-ready PDFs without a browser.

Send a `POST` request with your Markdown content, receive a binary PDF in response — no headless browser, no stored data. Whether you're generating invoices, reports, or AI-authored documents, Blink PDF slots into any stack in minutes.

<CardGroup cols={2}>
  <Card title="Quickstart" icon="rocket" href="/quickstart">
    Make your first API call and download a PDF in under five minutes.
  </Card>

  <Card title="API Reference" icon="code" href="/api-reference/overview">
    Full reference for the `POST /v1/render` endpoint, request body, and response headers.
  </Card>

  <Card title="AI & LLM Workflows" icon="robot" href="/guides/ai-llm-workflows">
    Pipe OpenAI or Claude output directly into Blink PDF for instant document generation.
  </Card>

  <Card title="Plans & Pricing" icon="tag" href="/plans/pricing">
    From a free tier (250 render units/month) to Pro, Business, and dedicated Enterprise plans.
  </Card>
</CardGroup>

## Why Blink PDF

Blink PDF uses a purpose-built render engine — there is no Chromium anywhere in the pipeline. That design unlocks a set of properties that browser-based renderers simply cannot offer:

* **Low-latency Markdown rendering.** No browser launch, no page load, no layout thrash.
* **No browser startup overhead.** The render engine avoids spawning Chromium for each document.
* **15 curated themes.** Pick a design preset with one field, then override anything per request. See [Themes](/configuration/themes).
* **Input never persisted.** Your Markdown is processed in memory and never stored; generated PDFs and staged assets are purged within 24 hours. See [Zero Retention](/concepts/zero-retention).
* **Reusable image assets.** Stage images once and reference them anywhere as `blink://asset/<id>` handles — they don't count toward your request size.
* **PDF/UA-1 accessibility.** Every PDF Blink generates is tagged for screen readers and passes accessibility audits out of the box.
* **Full Unicode and color emoji support.** Font subsetting ensures compact file sizes without sacrificing character coverage.

## Make your first API call

Send a `POST` request to `https://api.blinkpdf.io/v1/render` with your Markdown in the request body. The response is a raw PDF binary you can stream directly to your users or save to disk.

```bash theme={null}
curl https://api.blinkpdf.io/v1/render \
  --request POST \
  --header 'Accept: application/pdf' \
  --header 'Content-Type: application/json' \
  --header 'x-api-key: bp_xxxxxxxxxxxxxxxxxxxx' \
  --data '{
    "markdown": "# Invoice 0042\n\nHi Jane, thanks for your business!\n\n## What'\''s included\n\n- **Pro plan** subscription\n- Priority support\n\n**Total: $39** — paid on May 23, 2026.",
    "metadata": { "title": "Invoice 0042" }
  }' \
  --output invoice.pdf
```

The response arrives with `Content-Type: application/pdf` plus render-status and usage headers — `X-Request-Id` (include it when emailing [support@blinkpdf.io](mailto:support@blinkpdf.io)), `X-Render-Status` (`ok` or `degraded`), `X-Render-Rendered-As-Requested`, optional `X-Render-Diagnostics` (base64url-encoded JSON when the renderer raised issues), `X-BlinkPDF-Billing` (whether the render was billed) with `X-BlinkPDF-Usage-Event-Id`, and `X-BlinkPDF-Usage-*` (your render-unit usage against the plan). See the [API reference](/api-reference/overview#response-headers) for the full list.

<Tip>
  Ready to get your API key and try it live? Head to the [Quickstart](/quickstart) to be up and running in under five minutes.
</Tip>

## Integrations

Blink PDF works wherever HTTP works. First-class integration guides are available for **OpenAI**, **Claude**, **n8n**, **Make**, **Zapier**, **Notion**, **Obsidian**, and **Tiptap** — so you can add PDF generation to your existing automation or content workflow without writing infrastructure code.
