RatioReady
REST API

Automate your image processing workflow

Process images programmatically with a simple REST API. Integrates with Make.com, n8n, and any HTTP client.

Full Processing Suite

Clipart, wall art, poster, mockup, upscale, and DPI conversion — single image or batch, all via REST.

URL or File Upload

Submit images by direct URL (ideal for automation) or multipart file upload.

Async Job Polling

Long-running jobs return a job ID. Poll for status, download results when ready.

API Key Auth

Simple Bearer token authentication. Generate your key from your dashboard profile.

Batch Processing

Process up to 50 images per batch. ZIP download, individual file access, and automatic retry for failed images.

Webhook-friendly

Designed for no-code automation tools. Standard JSON request/response format.

Quick example

Request

# Wall Art package — 1 call, complete listing kit
curl -X POST https://api.ratioready.com/v1/batch/wallart \
  -H "Authorization: Bearer pk_your_api_key" \
  -F "images=@artwork.png" \
  -F 'payload={
    "userSetId": "ums_abc12345"
  }'

# 59 credits per image → includes:
#   • 5 ratio crops at 300 DPI (2:3, 3:4, 4:5, 11:14, A1)
#   • Bundled mockups
#   • Listing video
#   • Etsy listing PDF

Response

{
  "batchId": "batch-xyz-789",
  "status": "processing",
  "total": 1,
  "completed": 0,
  "failed": 0
}

// Poll GET /v1/batch/batch-xyz-789 →
{
  "status": "completed",
  "total": 1,
  "completed": 1,
  "downloadUrl": "/v1/batch/batch-xyz-789/download"
}

Packages vs Utilities

The API is organised around two pricing concepts. Most automations should call a package endpoint — utilities are reserved for one-off operations.

Packages — primary product

One call → complete listing kit

Print files, mockups, listing video, and Etsy PDF are all bundled into a single price.

  • POST /v1/batch/wallart59 cr / image
  • POST /v1/batch/poster55 cr / image
  • POST /v1/batch/clipart — bin formula (29 + 10·bin for JPG, +12 flat for PNG transparent)

Utilities — à la carte

Charged per use, for one-off ops

Reach for these only when you don't need the full package.

  • Upscale to 2K / 4K / 8K / 10K — 5 / 10 / 18 / 30 cr
  • Standalone mockup — 5 cr · listing video — 10 cr · listing PDF — 10 cr
  • Background removal — 3 cr · 300 DPI stamp — 1 cr

Always fetch live pricing at runtime: GET /v1/pricing/costs returns structured packages and utilities blocks.

Endpoint reference

Packages — the primary product

One call → complete listing kit. Use these for almost every automation.

Method Endpoint Auth
POST /v1/batch/wallart Bearer
POST /v1/batch/poster Bearer
POST /v1/batch/clipart Bearer

Job lifecycle — polling & downloads

Track and retrieve results from any package job.

Method Endpoint Auth
GET /v1/batch/:id Bearer
GET /v1/batch/:id/download Bearer
GET /v1/batch/:id/file Bearer
GET /v1/batch/:id/image/:idx/zip Bearer
POST /v1/batch/:id/retry Bearer

Standalone utilities — à la carte

Charged per use. Reach for these only when you do not need a full package.

Method Endpoint Auth
POST /v1/batch/upscale Bearer
POST /v1/mockup Bearer
POST /v1/dpi Bearer

Account & pricing

Read-only endpoints for account info and live pricing.

Method Endpoint Auth
GET /v1/me Bearer
GET /v1/me/history Bearer
GET /v1/pricing/costs Public
GET /v1/pricing/packs Public
GET /v1/pricing/plans Public
GET /v1/health Public

Legacy individual-file endpoints (/files/print/:i, /wallart/:ratio, /poster, /mockup/:i) are still supported for backward compatibility but new integrations should use /v1/batch/:id/file?type=….

Works with your tools

Make.com

Use the HTTP module to call any endpoint. Submit images by URL, poll for results, and route outputs to your next automation step.

n8n

Build workflows with the HTTP Request node. Chain image processing with listing creation on Etsy, Amazon, or Shopify.

Any HTTP client

Standard REST API with JSON responses. Works with curl, Python requests, Node.js fetch, or any language and framework.

Authentication

  1. 1 Create an account at ratioready.com/register
  2. 2 Go to your Profile page and generate an API key (starts with pk_)
  3. 3 Include it as a Bearer token: Authorization: Bearer pk_your_key

API FAQ