PUZRULIVE LOGIC PUZZLE
PUZRU DISTRIBUTION API

Free daily logic puzzle API for websites, apps and automations.

Read-only access to verified completed PUZRU 6×6 cage-sum puzzles. Get the same two-puzzle Daily set used by the embed, or retrieve one immutable completed World by round ID. Direct calls to puzru.com require no API key.

READ ONLY

No live Authority state, solutions, claim tokens or account data are exposed.

ARCHIVE BACKED

Responses come from verified completed puzzle history rather than a marketplace-specific generator.

CACHE FRIENDLY

Daily responses use ETag and shared-cache semantics; completed round responses are immutable.

Quick start

Use the Daily endpoint when you want a recurring warm-up plus challenge pair. Use the round endpoint when you need a stable archived puzzle.

Daily — two puzzles

curl -s https://puzru.com/api/distribution/v1/daily

One completed round

curl -s https://puzru.com/api/distribution/v1/puzzles/18291

JavaScript

const response = await fetch("https://puzru.com/api/distribution/v1/daily");
const daily = await response.json();
console.log(daily.set);

Python

import requests

daily = requests.get("https://puzru.com/api/distribution/v1/daily", timeout=10).json()
print(daily["set"])

Response model

Each puzzle contains a fixed size of 6, carried givens, addition cages, public difficulty metadata and URLs for the finished embed, playable surface and permanent puzzle page. The API never returns the canonical solution.

HTTP behavior

200 returns verified puzzle data. 404 means a Daily set is not ready or the requested completed round does not exist. 429 is fair-use rate limiting with Retry-After. 503 means the archive or marketplace authentication configuration is temporarily unavailable.

Caching and fair use

The Daily response can be cached for five minutes in browsers and one hour by shared caches, with stale-while-revalidate support. Completed round responses are immutable. Respect response cache headers instead of polling the same puzzle repeatedly.

Privacy and attribution

No PUZRU account is required. Optional direct integration source labels must be aggregate placement names only — never email addresses, account IDs or other personal identifiers. Responses include a small Powered by PUZRU attribution object.

Marketplace integrations

The same canonical API contract is packaged for RapidAPI and Apify. Marketplace requests are authenticated server-to-server and isolated from direct-IP rate-limit identities; the puzzle data itself is not forked or regenerated for a marketplace.

API or embed?

Choose the API when you are building your own presentation or automation. Choose Embed PUZRU when you want the complete responsive puzzle interface, daily progression and local solve experience without implementing the game UI.

LIVE WORLDJOIN NOW →