Meet the Werk24 API Console: From Sign-Up to a Working Integration in an Afternoon

· Written by Jochen MattesLangue d'origine : AnglaisVersion anglaise

Reading an engineering drawing with the Werk24 API has always been a few lines of code. Getting to those few lines — signing up, finding your key, understanding what to send, wiring it into your own application — used to mean a handful of emails and a doc tab that never quite matched your stack.

Today that changes. The Werk24 API Console is a self-service portal for everyone who calls the drawing-extraction API. Create an account, grab a key, watch your usage, manage your plan — and, with the new Integrate view, hand the whole integration to your AI coding agent as a single ready-to-paste prompt.

It lives at studio.werk24.io/console.


Sign up and get a key in minutes

The console opens with a short onboarding wizard: choose Pay as You Go or Production, enter your company and invoicing details and a card, then set your password from the email we send you. Pay as You Go has a one-time €1 card validation, credited back in full as usage. Production charges its first month at checkout instead. From the dashboard you then create your first API key. You sign in with your email and password.

From the dashboard you get everything a new integration needs in one place:

  • A getting-started checklist — copy your key, install the client, run a health check, send your first drawing, integrate the API.
  • Your API keys, masked once created, with a one-click copy and a quick test snippet.
  • Links to the API reference, the Python SDK, and extraction examples.

No spreadsheet of keys, no waiting on an account manager to provision access.

Keys, usage, and billing — all self-service

API Keys. Create as many keys as you need, name them, and set an error-notification email per key so failures reach the right inbox. A new key's secret is shown exactly once, then only ever stored as a hash — so keys stay keys, not liabilities. Delete a key the moment it's no longer needed.

Usage & Billing. See pages processed, included pages and a daily chart of your traffic. Invoices and payment methods are one click away through our billing partner.

Plans. Move between Pay as You Go and Production yourself, with no ticket required. Queue priority, data residency and encryption are add-ons on Production. Processing is in the EU; US processing is provisioned on request when booked. What each plan includes and which add-ons you can book are on the pricing page. Contract customers get a focused usage-only view, with no billing UI they don't need.


The Integrate view: let your coding agent do the wiring

This is the part we're most excited about.

Everyone integrates the Werk24 API into a different application, in a different language, at a different depth. Some teams just want to store the extracted JSON; others want a full upload → extract → review → export workflow with a drawing viewer. Writing one tutorial for all of that is impossible.

So instead of writing the integration for you, the console writes the prompt that lets your AI coding agent — Claude Code, Codex, or Cursor — build it inside your own codebase. You make two choices:

1. What do you want to build? Four levels, with honest effort estimates:

LevelWhat it doesEffort
Extract & StoreCall the API, save structured JSON to your database~1 hour
Display the DataRender the title block and a dimensions table in your UI~half a day
Balloon OverlayAn annotated drawing viewer — numbered balloons on the sheet, linked to a feature table~1 day
Full WorkflowUpload → extract → human review → export to your systems~2–3 days

2. Your application's language. Python ships an official client; TypeScript / Node, C# / .NET, Java, Go, and anything else point the agent at the Python client source as a reference for the WebSocket interface.

The console generates a complete werk24-integration-prompt.md on the spot — API essentials, the requirements for the level you chose, links to the docs, and a YOUR_API_KEY placeholder. Crucially, the prompt tells the agent to interview you first — your framework, where drawings enter the app, how you store results, what runs your background jobs — and to present a plan before it writes a single line. Then it builds against your real conventions instead of a generic template.

Three steps and you're integrating:

  1. Copy the prompt.
  2. Replace YOUR_API_KEY with a key from the API Keys page.
  3. Paste it into your coding agent and answer its questions.

An integration that used to be a weekend of doc-reading becomes a conversation with your agent — grounded in a prompt that already knows the API.


Try it

If you already have a Werk24 API key, sign in at studio.werk24.io/console and open the Integrate tab. Want to see the extraction quality first? Drop a drawing into the free browser demo, with no sign-up and no card. An API account requires a card. See the pricing page for the plans and signup details.

We built the console so that going from "curious" to "calling the API in production" is something you can do in an afternoon, on your own terms. We'd love to hear how far you get.