BiGapiguides
POST /v1/pdf/merge → 200 application/pdf · 1¢

Merge PDFs via API

Two or more files in, one PDF out, order preserved. Deterministic qpdf under the hood – no re-rendering, no quality loss.

Quick start (curl)

Get a key first – no signup: curl -X POST https://api.bigapi.dev/v1/keys (100 free operations, 7 days).

curl -X POST https://api.bigapi.dev/v1/pdf/merge -H 'Authorization: Bearer $KEY' -F 'files[]=@a.pdf' -F 'files[]=@b.pdf' -o merged.pdf

Give it to your agent (MCP)

Add BiGapi to Claude Desktop, Cursor or any MCP client – the server fetches its own key on first use:

{
  "mcpServers": {
    "bigapi": { "command": "npx", "args": ["-y", "@bigapi/mcp"] }
  }
}

Then simply ask: “Merge these three PDFs into one, in this order.” – the model calls the pdf_merge tool.

When your agent needs this

Parameters

ParamTypeRequiredNotes
filesfile[]yesTwo or more PDF files, field name files[].

Pricing

1¢ per operation
First 100 operations free (per key, 7 days) · failed calls (4xx/5xx) cost $0 · repeats with Idempotency-Key are free · prepaid credit from $5, never expires.

Every response carries X-BigAPI-Cost, X-BigAPI-Balance and X-BigAPI-Free-Ops – your agent can budget on its own.

Errors your agent can handle

StatusMeaningAgent action
401missing/invalid keyPOST /v1/keys for a fresh one
402credit exhaustedshow the upgrade_url from the response to a human
413file too largesplit the input (limit 100 MB)
422conversion failedcheck the detail field – costs $0
429rate limitedwait retry_after seconds

FAQ

Is there a file limit?

Up to 50 files per call, 100 MB each.

Does merging re-compress pages?

No – pages are copied structurally, bit-for-bit.

What about bookmarks and forms?

Page content is preserved; document-level metadata comes from the first file.