What you avoid by not building this yourself
- ✕
Weeks spent wiring up docxtemplater, deciding where to cache templates, figuring out PDF conversion.
- ✕
Edge cases: nested loops, conditional blocks, images, fonts rendering differently across servers.
- ✕
Managing the queue, storage bucket, signed URLs, retries, and downstream delivery.
- ✕
Writing the admin UI so non-developers can edit templates without a deploy.
How it works
- 1
Upload your template
Through the dashboard, a REST call, or the Payload-style admin. Store as many versions as you need.
- 2
Hit the API
POST a row (or thousands of rows) of JSON to the generate endpoint. Get back a URL to the finished file.
- 3
Ship it
Let SheetMergy email the output, or take the signed URL and do whatever you want with it.
Built by developers, for developers
REST API with keys per workspace
Standard HTTPS, API key auth, scoped per workspace. Rate-limited, not surprise-billed.
Sync or async
Get the file back in the response for small jobs, or poll a job endpoint for large batch runs.
DOCX, PDF, or email
One request, three possible outputs. Pick what makes sense for your integration.
Idempotent by default
Same request ID returns the same output. Safe to retry. No accidental double-charges.
Bring-your-own delivery
Drop into Gmail, S3, your webhook, or an email you control. Your product, your rules.
Multi-tenant ready
Used under the hood by agencies to power document features inside their own products.
Developer questions
- What's the request shape?
- POST /api/public/jobs/{id}/run with a JSON body of rows. Full OpenAPI spec is in the dashboard docs.
- Rate limits?
- Generous defaults; per-key throttles are visible in the dashboard. Bump limits via support for high-volume customers.
- How is pricing metered?
- Per credit: 1 credit per document, 1 per email. No per-request surcharge.
- Do you have client libraries?
- Official libraries are minimal — the API is plain HTTPS+JSON, so the dashboard has copy-paste curl and fetch examples in any stack.