Content & Documents · Integration
PDF4me
Add PDF4me to your product for your customers, and give your AI agents governed access to it.
PDF4me is a per-operation REST API: merge, split, convert, stamp, OCR, extract and barcode each have their own endpoint, and the document is sent as base64 content in the request body together with a document name rather than as multipart form data. Calls are POST only, so a GET against an operation endpoint returns a method not allowed rather than anything useful during testing. Larger jobs do not return the file inline: the service replies with an accepted status and a location to poll, and only a later call returns the produced binary, so a synchronous client will appear to receive nothing. Usage is metered in API credits per operation, which means a retry loop on a slow job can quietly consume a customer's balance. fastn holds each customer's PDF4me key, manages the polling and retries per tenant, and keeps credential upkeep out of your document pipeline.
In your product
Embedded for your customers. Per-tenant auth, no per-customer code, maintained by fastn.
Let a customer connect their own PDF4me account so document processing is billed to their credit balance
Merge generated statements and attachments into a single PDF before delivering it to the end customer
Split large scanned batches into per-record documents and file each one against the right entity
Run OCR on uploaded scans so the extracted text becomes searchable inside your product
For your AI agents
Governed, audited access for the agents you build, through the MCP server.
Let an agent assemble a document pack from named files while blocking any operation that would overwrite an original
Have an agent OCR an uploaded scan and answer questions from the extracted text
Audit per tenant which operations an agent triggered and how many credits each run consumed
Example prompt
Merge the signed contract and its two annexes into one PDF and give me the result.
Set up PDF4me in 4 steps
- 01Enable the PDF4me connector from your fastn dashboard.
- 02Have each customer authorise their own PDF4me account, so calls run under their credentials rather than a shared key.
- 03Decide which files, documents and versions your product needs, map those fields, then enable the actions and triggers you want.
- 04Call it from your product and expose it to your agents through the same governed connection.
Why teams use the PDF4me integration
What you get by embedding it with fastn instead of building it yourself.
- Ship a PDF4me integration without building it. Your customers connect their own PDF4me account inside your product and work their files, documents and versions there, with no per-customer code on your side.
- Handle the part that actually costs time: permissions and versioning are easy to get subtly wrong, and mistakes expose content. fastn owns the auth, token refresh, rate limits, pagination and breaking-change fixes, so a PDF4me update is not your on-call problem.
- One integration serves your product and your agents. The same governed PDF4me connection powers in-product features and gives AI agents scoped, audited access, so you let your product work with your customers' documents in place without wiring it twice.
Used by these teams
Compare with
Notion
Box
DocusignOften used alongside
Tools the same teams tend to run next to PDF4me, across other categories.
Shopify
Stripe
Jira
AsanaPDF4me integration FAQ
How do I add a PDF4me integration to my product?
Enable the PDF4me connector in your fastn dashboard, then let each customer authenticate their own PDF4me account. fastn handles the OAuth flow, token storage and refresh per tenant, so there is no PDF4me client code in your app and no per-customer branch in your codebase. Setup is 4 steps.
Do my customers each connect their own PDF4me account?
Yes. Every connection is scoped to the individual customer, so each authorises their own PDF4me account and only ever sees their own files, documents and versions. That per-tenant isolation is the point of an embedded integration: you support the long tail of customer setups without maintaining an integration per customer.
Can AI agents use this PDF4me integration?
Yes. The same connection is exposed to your agents through the fastn MCP gateway, with permissions scoped per tenant and every call audited. Let an agent assemble a document pack from named files while blocking any operation that would overwrite an original
Who maintains the PDF4me integration?
fastn does. When PDF4me changes an endpoint, deprecates a field or alters its auth, the fix lands in the connector rather than in your backlog, and your customers' connections keep working.
Whose permissions does the PDF4me integration run under?
Each customer's own PDF4me grant. Where PDF4me holds a library, their existing folder and item permissions apply and your product cannot reach content the connected account could not reach itself. Where it processes content you supply rather than storing it, the call runs under that customer's own credentials and is logged per tenant.
Can my product create or update content in PDF4me automatically?
Where PDF4me supports writes, documents, entries and assets can be created, updated and filed from your product or by an agent within scoped permissions, with each action logged. Where it is a read surface, the same connection serves reads only.
What can I build with the PDF4me integration?
A common starting point: let a customer connect their own PDF4me account so document processing is billed to their credit balance. Teams also use it for the other use cases listed above, and expose it to agents for governed reads and writes.
How much does the PDF4me integration cost?
It is included. Pricing is based on connected accounts, not on how many connectors you enable, so adding PDF4me does not change your per-connector cost. You can start free with 3 connected accounts.
Add PDF4me to your product
Start free with 3 connected accounts. No sales call required, and no per-customer integration code.