# Libraries and integrations

There is no official SDK yet — raw HTTP is the supported path. Where to find the Power Automate and Zapier connectors, generate a typed client, and MCP on the roadmap.

There is **no official SDK yet**. PDF Blocks is a clean HTTP API — one PDF in,
one PDF out — so raw HTTP is the supported, first-class path, and it works from
every language without a dependency to install. This page sets that expectation
and points each kind of reader to the right integration surface.

## Raw HTTP is first-class

Every action is a single `multipart/form-data` POST that returns a PDF. The
[Quickstart](/docs/api/quickstart) gets you a working call in a few minutes, and
every action reference page ships complete, runnable snippets in cURL, Python,
Ruby, Node.js, and C#. Paste one, swap in your key, and run.

If you want a typed client, generate one from the machine-readable contract —
see [OpenAPI specification](/docs/api/openapi-specification) for the codegen
tools and commands. That is the recommended way to get language-native models
and request methods until an official SDK exists.

## Where to go next

<CardGroup cols={2}>

<Card title="Generate a typed client" href="/docs/api/openapi-specification">
  Point OpenAPI Generator (or similar) at the spec for a client in your language.
</Card>

<Card title="Power Automate connector" href="/docs/power-automate/getting-started">
  Wire PDF actions into flows with no code — for Microsoft 365 automations.
</Card>

<Card title="Zapier connector" href="/docs/zapier/getting-started">
  Connect PDF actions to thousands of apps in Zaps, no code required.
</Card>

<Card title="Quickstart" href="/docs/api/quickstart">
  The fastest raw-HTTP path from an API key to a processed PDF.
</Card>

</CardGroup>

## Choosing a surface

- **Writing backend code or a script?** Call the API directly over HTTP, or
  generate a typed client from the [OpenAPI spec](/docs/api/openapi-specification).
- **Building a no-code or low-code automation?** Use the
  [Power Automate](/docs/power-automate/getting-started) or
  [Zapier](/docs/zapier/getting-started) connector.

## MCP — on the roadmap

A [Model Context Protocol](https://modelcontextprotocol.io) server, which would
let AI agents call PDF Blocks actions as tools, is on the roadmap and **not yet
available**. There is nothing to install today. Until it ships, agents should
call the HTTP API directly.