Send JSON to an endpoint and get back a finished invoice PDF. Line items, totals, and tax render from the data you already hold.
Billing data already lives in your database or your payment provider, but turning it into a document means a PDF library, a layout, and the maintenance that follows. That is weeks of work for a file you send every day.
Markup templates handle line items, page breaks, and totals that grow with the data.
POST the invoice as JSON, or upload a month of them as a CSV.
Store it, email it, or serve it from a link. Secure renders stay behind your API key.
Open one, change the parts you want, and it is yours. Every template is editable.
The same template runs from a REST call or from a spreadsheet. Pick whichever fits how your data already moves.
curl https://automette.com/api/v1/renders \
-H "Authorization: Bearer $AUTOMETTE_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"template_id": "cm4tpl8e20001js04xq2v9k3m",
"data": {
"invoice_number": "INV-0042",
"client_name": "Acme Corp",
"amount": "$4,200.00"
}
}'Returns a file URL. Read the API reference.
Upload a spreadsheet and get one file per row, packaged as a ZIP.
Put a URL in an email or a web page. It renders on first visit and is cached after that.
Fill the fields on the Generate page and download the result.
Design a template once. Connect any data source. Get perfect documents and visuals every time.
Build it visually, in code, or describe it to AI. Place fields where your data should go.
CSV, Google Sheet, form, webhook, or REST API, whichever fits your stack.
One, a thousand, or on demand, all from the same template.