POST /v1/imaging/image-favicon

Favicon set

Every size a browser or phone asks for, plus the .ico, from one source picture.

Make a favicon from an image now No key, no code — 2 credits either way.

curl -X POST "$DOATHING_API/v1/imaging/image-favicon" \
  -H "x-api-key: $DOATHING_KEY" \
  -H "content-type: application/json" \
  -d '{"file": {"filename": "photo.jpg", "content_type": "image/jpeg", "data_b64": "<base64>"}}'

Every size a browser or phone asks for, plus the .ico, from one source picture.

Generate a complete favicon set — multi-resolution .ico plus the PNG sizes browsers and phones request.

Input

Send a file object with base64 data_b64, its content_type and a filename. Accepted types: image/png, image/jpeg, image/webp, image/gif, image/tiff.

The declared type is not trusted — the bytes are sniffed and a contradiction is rejected rather than corrected.

Response

The result carries your remaining balance alongside it, so you can track spend without a second call.

{
  "ico": {
    "filename": "favicon.ico",
    "sizes": [
      16,
      32,
      48,
      64
    ]
  },
  "pngs": [
    {
      "size": 32,
      "filename": "favicon-32x32.png"
    }
  ],
  "html": "<link rel=\"icon\" href=\"/favicon.ico\" sizes=\"any\">",
  "request_id": "37f01edb-0163-42a1-ac51-0acaef979800",
  "credits_remaining": 96
}

Cost

2 credits per call, whether it is run from the site or from the API — the credential differs, the price does not. A new account starts with 20 credits.

A rejected request still costs a credit: the authorizer decrements before the tool validates. A call rejected for a missing or invalid key is free.

Parameters

Generated from the endpoint’s own validation, so this is exactly what it accepts. A body field goes at the top level; an option goes inside options.

NameInTypeDefaultNotes
backgroundoptionsstring#RRGGBB used to pad a non-square source to a square.