FileMorf Docs

Public API v1

Public API
Core Jobs

PDF Merge

Use the dedicated merge endpoint for multi-file PDF bundles. Upload every returned input before starting the job.

Base route

https://api.filemorf.com/api/public

Auth

Bearer API key created from the workspace.

Delivery model

Signed uploads, queued jobs, retained artifacts, refreshable URLs.

Dedicated endpoint

Multi-file PDF merge uses POST /merge

Merge is not modeled as a single upload URL because it requires multiple inputs. The merge endpoint returns one signed upload URL per file and one shared job id.

POST

/merge

Create a multi-file PDF merge job and receive one upload URL per input.

Sequence

Upload every merge input before starting the job

The merge job stays pending until you upload all required files and then explicitly queue it.

  • Create the merge job with the ordered files[] list and optional merge options.
  • PUT each file to its matching returned uploadUrl.
  • Call POST /jobs/:id/start once the full upload set is complete.
  • Poll GET /jobs/:id until the merged PDF is completed and downloadable.
Create merge job
curl -X POST https://api.filemorf.com/api/public/merge \
  -H "Authorization: Bearer $FILEMORF_API_KEY" \
  -H "Content-Type: application/json" \
  -H "Idempotency-Key: merger-2026-03-25-bundle-001" \
  -d '{
    "files": [
      {
        "filename": "part-a.pdf",
        "fileSize": 421067,
        "contentType": "application/pdf"
      },
      {
        "filename": "part-b.pdf",
        "fileSize": 412774,
        "contentType": "application/pdf"
      }
    ],
    "options": {
      "preserveBookmarks": true
    }
  }'

Next steps

Build against the live API, not the idea of it.

Create or rotate keys in the workspace, test against the base route, and use the same lifecycle documented here in production and local environments.