Use this puzzle generator API to create prefilled puzzle links from your application with authenticated HTTP requests. Send words, clues, a quote, or layout settings as JSON, receive a URL, and let your users preview, edit, and download in JigsawMake. One integration covers eight puzzle types without requiring your application to build their editors.
The response is a tool-page URL. PDF, PNG, and other exports happen after the user opens that page.
Try the APISign in to create an API key. Create and delete keys and view call history in your account.
Prefer AI tool discovery? See the Puzzle Generator MCP Server.
Choose a puzzle type and run its sample request against this website. The result panel shows the real JSON response rather than a prerecorded example. Open the returned link to check the supplied content and export a file. Editing a sample lets you test your own public vocabulary before you add the same request to your application.
Sign in to create or manage API keys. Your key stays in memory in this console.
Use public content. These settings will appear in the returned URL.
Configuration
HTTP APISign in to create or manage API keys. Your key stays in memory in this console.
Use public content. These settings will appear in the returned URL.
POST https://jigsawmake.com/api/v1/puzzle-links
Run a sample to see the response and a working preview link. No request is made until you press the button.
GET /api/v1/tools exposes the registered pages and parameter schemas. GET /api/v1/openapi supplies the OpenAPI 3.1 contract. Read those definitions before constructing requests: they describe the actual options the server checks, including permitted grid sizes and content limits. You can discover supported settings without reverse-engineering a browser form.
Your application supplies the word list, crossword clues, phrase, or dimensions. The link endpoint does not make a second paid AI request to invent content. A lesson builder can reuse its vocabulary, while an event app can pass its own bingo items. Content creation and puzzle configuration remain separate steps that your application controls.
The destination page applies the validated configuration to the existing generator. Users can review spelling, adjust settings, and download using that tool’s export controls. You do not need a PDF rendering service just to create a link. Available formats and any account restrictions remain those of the selected puzzle tool.
Sign in at /dashboard and create an API key. Send Authorization: Bearer YOUR_API_KEY on every API request. Request GET /api/v1/tools and choose a type. Use its optionsSchema to validate inputs before submission. The optional page field selects a registered page in that same category; it cannot redirect to an arbitrary external website.
POST to /api/v1/puzzle-links with Content-Type: application/json. Supply type and options, plus page when needed. For a word search, provide the words and gridSize. For a crossword, send word-and-clue objects rather than only a topic.
On success, read data.url and data.options. The normalized options show the effective settings, including defaults. Handle non-success responses before displaying a link: a validation error contains an error message and may include field-level details.
Render the URL as a normal link in your application. The browser generator previews the puzzle, then its Download or Export menu saves the file. A successful API call means the configuration link exists; it does not mean a PDF has already been downloaded.
All eight categories share the same link endpoint. They accept different content, so use the catalog’s schema for each category rather than forcing every request into a single generic text field. Word Search and Crossword API examples are included in the live console. The catalog also lists the existing themed pages available through the optional page field.
| Puzzle | API type | Sample input fields | What you can create |
|---|---|---|---|
| Jigsaw APIJigsaw Generator | jigsaw | shape, tilesX, tilesY, sizeX, sizeY, seed | Configure piece counts, shape, dimensions, and a seed for a cut-pattern preview. Add an optional HTTPS image URL for a photo puzzle. |
| Word Search APIWord Search Generator | word-search | title, words, gridSize, diagonal | Supply a word list, grid size, and direction settings to prepare a vocabulary worksheet that users can review in the browser. |
| Crossword APICrossword Generator | crossword | title, clues | Send answer-and-clue pairs for a connected crossword preview. Review placement in the editor before exporting the worksheet. |
| Sudoku APISudoku Generator | sudoku | gridSize, difficulty, pageCount, puzzlesPerPage, paperSize | Choose grid size, difficulty, puzzles per page, and paper size. The browser generates the Sudoku worksheet and handles its downloads. |
| Bingo APIBingo Generator | bingo | title, gridSize, cardCount, items | Provide custom bingo items or choose a blank template, along with grid size and card count. Open the link to review the cards before printing. |
| Maze APIMaze Generator | maze | cols, rows, algorithm, seed | Choose rows, columns, an algorithm, and an optional seed. Preview the maze and use the browser’s puzzle and answer-key downloads. |
| Cryptogram APICryptogram Generator | cryptogram | sourceText, difficulty | Supply a phrase and difficulty for a letter-substitution activity. Review the cipher and save the worksheet through the browser editor. |
| Word Scramble APIWord Scramble Generator | word-scramble | words, difficulty | Supply five to twenty-five English words and a difficulty. Review the shuffled spelling activity before saving a worksheet or using online play. |
The JSON response contains data.type, data.page, data.url, data.options, data.resultType, and data.instructions. resultType is tool_page. The URL includes the versioned configuration and API attribution parameters. It is not a hosted file, a persisted puzzle ID, or a guarantee that reopening will reproduce the same randomized worksheet.
Requests are limited to 32 KiB and generated links to 8,000 characters. Unknown fields, unsupported combinations, and pages from another category are rejected with 400. Malformed JSON also returns 400; oversized bodies return 413; an incorrect content type returns 415. Limit responses use 429 and Retry-After. Each account can make 120 API and MCP requests per minute across its keys and server instances. A per-process IP limit is an additional backstop for link creation.
The link API requires an API key created after signing in. Send it in the Authorization Bearer header, never in a URL. Delete keys and view authenticated call history in your account. Keep the content suitable for a public URL because query parameters can appear in history and analytics. Jigsaw and Maze accept seeds; other randomized generators may change when reopened. Store your input configuration if your workflow needs to recreate a request, and let the user download a finished file when an exact artifact must be retained.
Request GET /api/v1/tools with your API key, and read the OpenAPI schema for the complete parameter definitions. Keep production keys in your backend; the JavaScript sample is for a trusted environment.
cURL example
curl https://jigsawmake.com/api/v1/puzzle-links \
-H 'Authorization: Bearer YOUR_API_KEY' \
-H 'Content-Type: application/json' \
-d '{"type":"word-search","options":{"title":"Ocean Life","words":["WHALE","SHARK","CORAL","DOLPHIN"],"gridSize":12,"diagonal":false}}'JavaScript example
const response = await fetch("https://jigsawmake.com/api/v1/puzzle-links", {
method: "POST",
headers: { "Content-Type": "application/json", "Authorization": "Bearer YOUR_API_KEY" },
body: JSON.stringify({
"type": "word-search",
"options": {
"title": "Ocean Life",
"words": [
"WHALE",
"SHARK",
"CORAL",
"DOLPHIN"
],
"gridSize": 12,
"diagonal": false
}
})
});
const payload = await response.json();
if (!response.ok) throw new Error(payload.error);
console.log(payload.data.url);Pass a lesson’s words into the Word Search API or turn definitions into crossword clues. Let a teacher check the worksheet before printing instead of sending an unreviewed file straight to a class.
Build bingo links from a host’s item list. The browser handles card previews and downloads; your application keeps responsibility for collecting the attendee-appropriate words and selecting a supported card size.
Offer a puzzle activity beside a lesson. Link creation can run in your backend with a private API key, and the learner or teacher completes the preview-and-download step on the destination page.
Pass jigsaw dimensions in millimeters, shape, tile counts, and an optional seed. For photo puzzles, supply a CORS-compatible HTTPS image URL or let the user upload an image in the editor.
Use an HTTP request step to prepare links from public rows in a spreadsheet or content database. Send those links into your own approved publishing workflow; this API itself does not email or post results.
Match a recommendation to a supported Sudoku or Maze configuration. A link is useful when people should choose their final print settings; it is less suitable when your application must receive a file with no browser interaction.
No. POST /api/v1/puzzle-links returns JSON containing a prefilled tool-page URL. The user opens that URL, reviews the generated preview, and downloads with the browser’s Export or Download controls. If your application requires a server-generated binary file in the HTTP response, this link-based API does not currently provide that workflow.
Yes. Use type word-search with a words array and grid settings, or type crossword with a clues array containing word and clue pairs. Both use the shared puzzle-links endpoint. They return editor links, so the browser remains responsible for the grid preview and file export rather than returning a standalone grid or PDF directly.
Yes. Sign in and create a key in your account. The full key is shown only once; save it securely. Send it in the Authorization Bearer header. Deleting a key blocks future calls and retains its call history. Requests remain subject to validation, body-size limits, URL-length limits, and rate limiting. The destination tool may have its own account or premium rules for particular features; access to the link endpoint does not bypass those controls.
The HTTP endpoints support CORS and JSON requests with an Authorization Bearer header. The console keeps your key in memory. For a deployed application, call through your backend so visitors cannot extract your API key from frontend code. Check response.ok before reading data.url and handle validation errors in your own interface. The live example uses this same request flow. Use the OpenAPI contract or catalog schema to construct supported inputs for the selected puzzle category.
Not always. The link carries settings rather than a stored puzzle. Jigsaw and Maze support a seed for repeatable generation with the same remaining configuration. Other puzzle types can produce a fresh randomized arrangement when reopened. Keep a downloaded file when your workflow needs the exact worksheet rather than only its input settings.
Use HTTP when your application or automation already constructs requests and handles JSON responses. Use MCP when an AI host should discover the tools and supply arguments through its tool-calling interface. Both interfaces share the supported puzzle options and return tool-page links. Neither interface adds a separate server-side file-rendering step.
Inspect these browser tools before choosing an integration. The Word Search editor shows how supplied vocabulary becomes a worksheet; the Crossword editor handles word-and-clue pairs; the Jigsaw editor exposes shape and export controls. For an AI host rather than an application backend, follow the separate MCP setup guide linked below.
Try a sample request, open the returned puzzle link, and download from the browser editor.