MockFrame
Start free

HTTP automations

Screenshot mockup automations for Zapier, Make and n8n

Put screenshot rendering inside the tools you already use.

The alpha API works with generic HTTP and webhook steps today. A marketplace app is not required to test the workflow.

01

Zapier

Add Webhooks by Zapier, choose POST, and send JSON to https://mockframe.app/api/v1/render.

02

Make

Add an HTTP Make a request module, choose POST, and set the body type to application/json.

03

n8n

Use an HTTP Request node with POST and return the response as text for SVG output.

Which endpoint to call

/api/v1/screenshots
Device mockups and store screenshot sets as PNG or JPEG links. Needs a Pro API key in the Authorization header (or x-api-key). Screenshots can be public https URLs. The image links last 24 hours, so add a step that downloads or uploads them.
/api/v1/render
A screenshot on a gradient as one self-contained SVG. Works without a key for up to 50 cards a day; with a key it counts toward your daily requests. The screenshot must be a PNG, JPEG or WebP data URL, and the body must stay under 3.5 MB.

Device mockups from a public image URL

Map the request below into the HTTP step: method, URL, the two headers and the JSON body. Map images[0].url from the response into your next step.

Request
POST https://mockframe.app/api/v1/screenshots
Authorization: Bearer mf_live_…
Content-Type: application/json

{
  "screenshots": ["https://example.com/home.png"],
  "device": "auto",
  "look": "glow"
}
Response
{
  "images": [
    { "name": "mockup-1.png", "width": 1080, "height": 1350, "url": "https://…" }
  ],
  "expiresAt": "…"
}

An SVG screenshot card, no key needed

The response body is the SVG itself, so read it as text. In n8n, set the HTTP Request node's response format to text.

Request
POST https://mockframe.app/api/v1/render
Content-Type: application/json

{
  "template": "beautify-screenshot",
  "screenshot": "data:image/png;base64,…",
  "width": 1200,
  "height": 900,
  "backgroundFrom": "#6d28d9",
  "backgroundTo": "#0e7490"
}

Workflows people build

New release, new store images

When a build is tagged, send its screenshots to /api/v1/screenshots with type store-set and get back eight App Store or Google Play listing images with captions.

Screenshots from a shared folder

When a file lands in a cloud folder, pass its public link to /api/v1/screenshots and save the framed mockup next to it.

Changelog and social images

When a changelog entry is published, turn its screenshot into an SVG card on a gradient with /api/v1/render, without an API key.

Errors come back as JSON with an error message and a status: 400 for a bad request, 401 for a missing or revoked key, 402 without Pro and 429 once the day's requests are used.

Send the same body documented by the Render API. During alpha, use data URLs from a trusted storage step and keep the request below the documented input limit.

View API contract