Settings & API keys#

The Settings page tunes the workspace across seven tabs: issuer, preferences, numbering, tracking, sources, API keys, webhooks.

The emitter profile#

Name, address, tax ID, IBAN, phone, e-mail, legal mentions: this data feeds the {{COMPANY.*}} variables of every template (reference). Fill it once — it is step 1 of the onboarding.

Preferences#

The Preferences tab sets the workspace default currency: it applies to the amount fields of your documents — form, schema and PDF render — unless a template explicitly sets its own. A preview shows the formatting as you choose.

You can also create custom currencies, outside the ISO registry: points, credits… Each one carries a three-letter code, a label, a symbol and a number of decimals, and becomes selectable wherever a currency is asked for.

Numbering and tracking#

Per-template numbering is composed here (patterns and tokens). The Tracking tab is the workspace catalogue: it defines the available dimensions (e.g. payment, delivery) with their options and colours. Application is then configured template by template, in the template details (“Attached tracking”): only documents from those templates show and fill in this tracking.

API keys#

Keys tab: create a workspace key (dfk_…), shown only once — copy it immediately. It carries its workspace scope and is used as Authorization: Bearer on /api/v1 (quickstart). Revoke immediately on leak.

Webhooks#

The Webhooks tab declares the URLs DokKraft calls when your workspace produces events (document issued, PDF ready…) — subscription, secret and signature verification are covered in the integration docs.

Try without coding: the playground#

The sidebar API Playground section tries the API from the browser: the form is generated from the template schema, curl / Node / Python / PHP snippets project live, execution goes through your session (no key ever exposed) and does not count against the quota — Sandbox badge. The ideal way to validate a template before wiring your software.