Doc2api

Integration

Generate PDFs from Make

Make is good at the shape of the data and less good at producing a document from it. This is the module that does the second part, and it is one HTTP call.

There is no official Make app yet. This uses Make's own HTTP and webhook steps, which is fully supported and takes about five minutes. If you would rather have a one-click app, email support@doc2api.co — demand is how we decide what to build next.

1. Send the values, get a document

Add a HTTP → Make a request step and point it at your template's fill endpoint. Use your workspace's automation key — one key for everything, from your dashboard — rather than a per-template key, so you only paste a credential once however many automations you build.

Need the template id? GET /api/v1/templates lists them all by name with the same key, and GET /api/v1/me confirms the key works before you build anything on it.

MethodPOST
URLhttps://www.doc2api.co/api/v1/templates/<TEMPLATE_ID>/fill
HeaderX-Api-Key: d2a_auto_…
HeaderContent-Type: application/json

Body — your field names, under `data`:

{
  "data": {
    "customer_name": "Sarah Whitfield",
    "invoice_ref": "INV-0042",
    "amount_due": "1350.00"
  },
  "params": { "order_id": "A-1029" }
}

The completed PDF comes back in the response. Add "preview": true while you are building the automation — the first 100 of those each month do not count against your documents.

2. Or have it delivered to you

Add a Webhooks → Custom webhook step, copy the URL it gives you, and paste it into your template's webhook settings. Every completed document then arrives there on its own — with retries if Make is briefly unreachable, which the synchronous call above cannot give you.

The delivery is signed, so you can prove it came from us: how to verify the signature.

Worth knowing about Make

  • Set Body type to Raw with a JSON content type, and add X-Api-Key under Headers.
  • Tick “Parse response” and Make will map our JSON reply into later modules for you.
  • The reply carries a pdf_url rather than the bytes. Feed that straight into a Google Drive, Dropbox or email module — no base64 step.

Get a template and a key first

Upload the PDF you need filled, or design one, and you have the endpoint and key this needs. No account required to try it.