# APITemplate.io integrations: PDFs and images

> Create a PDF, create an image and update a PDF template in APITemplate.io, and start a workflow when APITemplate.io sends “PDF generated”.

**Canonical page:** https://tray.ai/connectors/apitemplate-io-integrations/
**Categories:** Documents and e-signature
**Connects through:** HTTP Connector

## Overview

APITemplate.io generates PDFs and images from reusable templates, HTML, Markdown or a web page URL, with regional endpoints in the US, Europe, Singapore and Australia. Tray.ai connects to APITemplate.io through the HTTP Connector, so your workflows can call the APITemplate.io API alongside the rest of your stack.

## Use cases

### PDFs

Create and update pdfs in APITemplate.io from any Tray.ai workflow. The APITemplate.io API covers calls such as create a PDF and create a PDF from HTML.

- Create a PDF
- Create a PDF from HTML
- Create a PDF from URL

### Images

Read, create, and delete images in APITemplate.io from any Tray.ai workflow. The APITemplate.io API covers calls such as create an image and list generated objects.

- Create an image
- List generated objects
- Delete an object

### Templates

Read and update templates in APITemplate.io from any Tray.ai workflow. The APITemplate.io API covers calls such as list templates and get a PDF template.

- List templates
- Get a PDF template
- Update a PDF template

### Account

Read account in APITemplate.io from any Tray.ai workflow. The APITemplate.io API covers calls such as get account information and check remaining quota.

- Get account information
- Check remaining quota

## Challenges Tray.ai solves

### Keeping APITemplate.io credentials out of logs

A raw API call usually means pasting a key or token into the request, where it ends up in step inputs, logs, and screenshots.

**How Tray.ai helps:** Store APITemplate.io credentials once as a Tray.ai authentication and reference them from the HTTP Connector. Tray.ai masks authentication values in logs, so the secret never shows up in a step's input or output.

### Going from the APITemplate.io API docs to a working call

Translating an example request from API docs into a workflow step means copying the method, URL, headers, and body by hand.

**How Tray.ai helps:** Paste a cURL example from the APITemplate.io API docs into the HTTP Connector and Tray.ai fills in the method, URL, headers, and body for you.

### Handling files and non-JSON responses

Not every API answers in JSON. Some return XML, files, or binary data, or expect a multipart upload.

**How Tray.ai helps:** The HTTP Connector parses JSON and XML responses, returns files you can pass to the next step, and sends multipart form data for uploads.

## Frequently asked questions

### Does Tray.ai connect to APITemplate.io?

Yes. Tray.ai connects to APITemplate.io through the HTTP Connector, which calls the APITemplate.io API directly. Any call the APITemplate.io API documents can run as a step in a Tray.ai workflow.

### How does Tray.ai authenticate with APITemplate.io?

The APITemplate.io API uses an API key in a request header. You save it once as a Tray.ai authentication, and the HTTP Connector adds it to every request.

### Can I get a dedicated APITemplate.io connector?

APITemplate.io runs through the HTTP Connector rather than a dedicated connector. If your team wants one, the Tray.ai connector SDK can build a dedicated APITemplate.io connector from the APITemplate.io API.

## Learn more

- Intelligent Integration: https://tray.ai/platform/intelligent-ipaas/
- Merlin Agent Builder: https://tray.ai/platform/merlin-agent-builder/
- Agent Gateway for MCP: https://tray.ai/platform/agent-gateway/
- Book a demo: https://tray.ai/contact/