Skip to main content
POST
Merge PDFs

Description

This endpoint merges multiple PDF files into a single PDF.

Endpoint

Headers

  • Content-Type: application/json
  • Authorization: Bearer <API_KEY> (required)

Request Body

Responses

Success (200)

Returns the URL of the merged PDF.

Notes

  • Credit usage: 50 credits per 100MB of output PDF size
  • Requires at least 2 PDF files to merge
  • Optional PDF/A and PDF/UA compliance
  • Optional metadata for the merged PDF
  • Files are temporarily stored (24-hour retention)

Rate Limiting

Rate limit headers are included in the response.

Authorizations

Authorization
string
header
required

Bearer authentication header of the form Bearer <token>, where <token> is your auth token.

Body

application/json
inputMethod
enum<string>
required

Indicates whether binary content is supplied via URL or base64-encoded string.

Available options:
url,
base64
files
string[]
required

Array of PDF URLs or base64-encoded PDF contents to merge.

Minimum array length: 2
metadata
object

Optional metadata map to embed within the merged PDF.

pdfa
enum<string>

Optional PDF/A compliance level to apply when merging.

Available options:
PDF/A-1b,
PDF/A-2b,
PDF/A-3b
pdfua
boolean

Whether to attempt enabling PDF/UA compliance.

requestSource
enum<string>

Optional identifier describing where the API request originated.

Available options:
API,
WEB,
MAKE_DOT_COM,
ZAPIER,
N8N,
PLAYGROUND,
DEFAULT_AUTOMATION,
AGENT_PREVIEW,
AGENT_LIVE,
AUTOPILOT,
STUDIO

Response

Merged PDF returned.

url
string<uri>
required

Temporary download URL for the merged PDF.