How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Renderwolf API

Production REST/JSON rendering API: screenshots, PDFs, templated images, QR codes, video, site previews, signed URLs, async jobs, batches, destinations/deliveries and usage. Bearer API-key auth.

This API exposes 33 operations across 25 paths, organized into 7 resource areas, and defines 17 schemas. It is described by OpenAPI 3.1.0, at version 1.0.0.

Requests are made against 2 base URLs: https://api.ironfang.uk/renderwolf, https://api.ironfang.uk.

33 operations 25 paths 17 schemas 3 DELETE15 GET1 PATCH13 POST1 PUT

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.1.0
API Version
1.0.0
Base URL
https://api.ironfang.uk/renderwolf
Authentication
HTTP Bearer
Contact
Terms of Service
Resource Areas
7

Authentication & Security 1

Renderwolf API declares 1 security scheme for authenticating requests. It accepts HTTP bearer tokens (apiKey). By default, every request must be authenticated.

  • apiKey — An API key from the portal, sent as Authorization: Bearer rwlive....

Paths & Operations 33

Across 25 paths, the API surfaces 33 operations — 3 DELETE, 15 GET, 1 PATCH, 13 POST, 1 PUT. They span 7 resource areas: Render, Templates, Signed URLs, Account, Jobs, Batches, Destinations. Each is listed below with its method, path, parameters, and response codes.

Render 5

Turn a URL or HTML into an image, PDF or video.

POST
/v1/screenshot
Render a screenshot
createScreenshot body → 200400401422429
POST
/v1/qr
Render a QR code
createQr body → 200400401422429
POST
/v1/pdf
Render a PDF
createPdf body → 200400401422429
POST
/v1/video
Render a clip
createClip body → 200400401422429501
POST
/v1/site-preview
Render a scrolling website preview
createSitePreview body → 200400401422429501
Templates 6

Stored HTML with {{variable}} placeholders, rendered on demand.

GET
/v1/templates
List templates
listTemplates → 200401
POST
/v1/templates
Create a template
createTemplate body → 201400401
GET
/v1/templates/{id}
Fetch a template
getTemplate 1 param → 200401404
PUT
/v1/templates/{id}
Replace a template
updateTemplate 1 param body → 200400401404
DELETE
/v1/templates/{id}
Delete a template
deleteTemplate 1 param → 204401404
POST
/v1/image/{id}
Render a template
renderTemplate 1 param body → 200400401404422429
Signed URLs 2

Shareable render URLs that need no API key.

POST
/v1/sign
Mint a signed render URL
createSignedUrl body → 200400401404501
GET
/v1/r/{exp}/{sig}
Render from a signed URL
renderSignedUrl 2 params → 200403404429
Account 3

Usage against quota.

GET
/v1/capabilities
What Renderwolf does, is building and does not offer
getCapabilities → 200
GET
/v1/requests
Request history
listRequests 10 params → 200400
GET
/v1/usage
Usage this period
getUsage → 200401
Jobs 6
POST
/v1/jobs
Submit a durable render job
submitJob body → 202200400403404409429501
GET
/v1/jobs
List jobs
listJobs 3 params → 200
GET
/v1/jobs/{id}
Poll a job
getJob 1 param → 200404
DELETE
/v1/jobs/{id}
Cancel a job
cancelJob 1 param → 200404409
GET
/v1/jobs/{id}/result
Collect a job's result
getJobResult 1 param → 302404409410
GET
/v1/results/{exp}/{sig}
Signed result download
getSignedResult 3 params → 200403410
Batches 2

Up to 100 renders submitted, and refused, together.

POST
/v1/batches
Submit up to 100 jobs together
submitBatch body → 202400403429
GET
/v1/batches/{id}
Poll a batch
getBatch 1 param → 200404
Destinations 9

Where a finished job goes - a signed webhook, or your own S3 bucket.

POST
/v1/destinations
Register a delivery destination
createDestination body → 201400403501
GET
/v1/destinations
List destinations
listDestinations → 200
GET
/v1/destinations/{id}
Get a destination
getDestination 1 param → 200404
PATCH
/v1/destinations/{id}
Rename or enable a destination
updateDestination 1 param body → 200404
DELETE
/v1/destinations/{id}
Remove a destination
deleteDestination 1 param → 204404
POST
/v1/destinations/{id}/test
Test a destination now
testDestination 1 param → 200404
GET
/v1/deliveries
List deliveries
listDeliveries 3 params → 200
GET
/v1/deliveries/{id}
One delivery, with the body it posted
getDelivery 1 param → 200404
POST
/v1/deliveries/{id}/redeliver
Send a delivery again
redeliverDelivery 1 param → 200404

Schemas 17

The contract defines 17 schemas that model the data the API accepts and returns. The most detailed are QrRequest (13 properties), RenderCommon (12 properties), Usage (9 properties), SignRequest (8 properties). Each schema is shown below with its type and property counts.

Error
object
1 property 1 required
Cookie
object
4 properties 2 required
Clip
object
A rectangle in CSS pixels from the top left of the page.
4 properties 2 required
Margin
object
Page margins in inches. Omitted sides keep Chromium's default rather than becoming zero - a PDF printed hard to the paper edge is rarely what leaving a field o…
4 properties
RenderCommon
object
12 properties
QrRequest
object
13 properties 1 required
JobDelivery
object
Where this job goes when it finishes, by destination id. Register the destination first; credentials are never sent here. A webhook fires on success, failure a…
3 properties
ScreenshotRequest
SitePreviewRequest
ClipRequest
object
Everything is optional. With no background a solid colour is used, which is what most captioned clips want.
8 properties
PdfRequest
TemplateInput
object
4 properties 2 required
Template
object
7 properties
RenderTemplateRequest
SignRequest
object
8 properties 1 required
SignedUrl
object
2 properties
Usage
object
9 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

ironfang-openapi.yaml Raw ↑
Where this information came from

This is an independent, third-party profile of Renderwolf API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.