API documentation

Overview

How rendering works

You create a template in Templar (HTML with Handlebars). The render API loads that template for your account, merges your data object, produces a PDF, and responds with JSON that includes a full absolute url to the file use that value directly; you do not need to combine it with a separate base. Each successful render consumes one credit.

Authentication

API keys

Every request must include a valid key in the Authorization header using the Bearer scheme (same as the in-app playground).

Authorization: Bearer <YOUR_API_KEY>

Endpoint

Render PDF

const res = await fetch(`https://templar.odysii.in/api/pdf/render`, {
  method: "POST",
  headers: {
    "Content-Type": "application/json",
    Authorization: `Bearer YOUR_API_KEY`,
  },
  body: JSON.stringify({
  "templateName": "my-invoice",
  "data": {
    "invoice_no": "INV-001",
    "client_name": "Acme Corp",
    "total": 4200
  },
  "pageSize": "letter"
}),
});

const json = await res.json();
console.log(json);

Request body

Parameters

Success

Responses

On 200, the body matches what the playground shows in the response panel: a JSON object with a downloadable PDF location and a short message.

{
  "url": "https://your-origin/outputs/pdf-… .pdf",
  "message": "PDF generated Successfully"
}

The client parses JSON from the response text; if parsing fails, the playground falls back to a raw text wrapper, your integration should prefer checking res.ok and reading json.error on failures.

Errors

HTTP status reference

Error bodies use { "error": "…" } with the messages below (same strings returned by the API).