This tutorial covers how to get started with the Microlink API — authentication, key parameters, and code examples. We also show why developers often end up choosing a simpler alternative.
Microlink (Screenshot, metadata, PDF in one open-source API) provides a REST API for url + metadata extraction. Here's how to set it up and make your first API call.
Most Microlink API requests require authentication via API key. You'll find your key in the Microlink dashboard after signing up.
No raw HTML input — you must host the content before capturing it. No native n8n or Make.com node. No built-in batch endpoint.
If you're using Microlink specifically for HTML-to-image rendering and find the setup complex, RenderPix offers a simpler API with native n8n support:
| Feature | Microlink | RenderPix |
|---|---|---|
| Starting price | $9/mo | $9/mo |
| Free tier | limited | 100 renders/mo |
| Raw HTML input | ✗ | ✓ Full HTML/CSS |
| n8n native node | ✗ | ✓ Native node |
| Batch rendering | ✗ | ✓ Built-in |
| Template variables | ✗ | ✓ {key} syntax |
| Async callback | ✗ | ✓ |
| PNG / JPEG / WebP | ✓ | ✓ |
| Primary use case | URL + metadata extraction | HTML image generation |
100 renders/month on the free plan. Full HTML control. Native n8n node.
Get your free API key →