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: 5 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
Bearer authentication header of the form Bearer <token>
, where <token>
is your auth token.
Body
application/json
Indicates whether binary content is supplied via URL or base64-encoded string.
Available options:
url
, base64
Array of PDF URLs or base64-encoded PDF contents to merge.
Minimum length:
2
Optional metadata map to embed within the merged PDF.
Optional PDF/A compliance level to apply when merging.
Available options:
PDF/A-1b
, PDF/A-2b
, PDF/A-3b
Whether to attempt enabling PDF/UA compliance.
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.
Temporary download URL for the merged PDF.