What's new

Historical release reconciliation

• Invoicing and compliance — Added Croatian B2C fiscalization support, country tax-rate improvements, document API enhancements, and registration-number support.

• Product experience — Improved account navigation, entity management, translations, theme controls, and document PDF verification.

• Documentation and integrations — Expanded API and SDK documentation, validation examples, AI-readable docs, webhooks, and HAL/widget integrations.

• add tax detail page similar to customers and translated tax… add tax detail page similar to customers and translated tax add/edit and other if needed

• Add light/dark switch to login/signup/reset to web app… Add light/dark switch to login/signup/reset to web app similarly to how it's implemented when logged in

• Plan adding posthog to project to best utilize the tool Plan adding posthog to project to best utilize the tool

• If user is identified via widget and they have a… If user is identified via widget and they have a subscription plan we could move them to won stage in crm

• Reorganize docs sidebar navigation The documentation sidebar items need to be reviewed and reordered for better logical flow and grouping.

Current Issues Identified

API Reference (api-sidebar.json)

1. Document endpoint ordering is inconsistent - Within each document type (Invoices, Estimates, etc.), endpoints appear in arbitrary order. Should follow a logical flow:

   • Object description
   • Create → List → Get by ID → Update → Delete/Void (CRUD operations)
   • Version history endpoints
   • Rendering (Preview, HTML, PDF)
   • Sharing operations (Make shareable, Get token, View shareable, Unshare)
   • Draft operations (Finalize, Delete draft)
   • Document number preview

2. "Other" section is a catch-all - Contains disparate items:

   • Email (could be Communication)
   • Exports
   • Activities (audit logs)
   • White Labels + White-Label Subscriptions (related, should be grouped)

3. Files & Uploads - Has "Files" and "Upload" as separate collapsed items but they're closely related

Guides Section (astro.config.mjs)

The current order seems reasonable but could verify:

• Getting Started: Introduction → Core Concepts → Quickstart → Authentication → Idempotency
• Guides: Use Cases → Documents → Data → Compliance

Recommended Changes

1. Reorder document endpoints in api-sidebar.json to follow consistent CRUD-first pattern
2. Consider renaming "Other" or reorganizing its contents
3. Potentially merge Files and Upload under one heading
4. Review if any guides should be reordered based on user journey

• user is requesting create document endpoint with all… user is requesting create document endpoint with all features but skipping calculation so they can pass their own sums, the rest of the logc and expected data for db should be the same, can we produce something like that with minimal changes mbybe by flag or separate endpint?

• Conditional root redirect by account type Change the root / route to redirect based on account type:

• White-label accounts (entity-only): Redirect to /app

• Root accounts (Space Invoices users with account access): Redirect to /account

Currently / always redirects to /app unconditionally. Should use the existing getPostLoginRedirect utility logic.

• Verify bank account info on document PDFs

• Fix sandbox toggle and developer translations Fixed sandbox toggle in account sidebar - dark text was not visible against orange background. Changed to white text on solid orange background. Also removed i18n translations from Developers sidebar menu (English only for developer features).

• Fix menu items elements not translated Fix menu items elements not translated

• Fix entity add page bugs Fixed three bugs on the entity add page:

1. Entity created in wrong environment: When adding entity from /account in sandbox mode, it was created in live. Fixed by passing environment prop through CreateEntityForm.

2. Back button context-awareness: Back button always went to /app. Now uses session storage flag to determine origin - goes to /account if user came from there.

3. Missing sandbox banner: Add entity page didn't show sandbox banner because it checked active entity (which doesn't exist yet). Switched to AccountSandboxBanner which checks environment from context.

Also created UserProvider for clean access to user data and isAccountUser check (regular vs white-label user).

• Add SDK documentation to docs site Add comprehensive documentation for all three SDK packages to the docs site:

• JavaScript SDK (@spaceinvoices/js-sdk): TypeScript SDK auto-generated from OpenAPI

• Embed SDK (@spaceinvoices/embed-sdk): Iframe-based UI embedding for quick integration

• React UI (@spaceinvoices/react-ui): Copy-paste React components

This includes creating a new "SDKs" sidebar section, documentation pages for each SDK, and code examples.

• remove everything related to notes as it was a test remove everything related to notes as it was a test

• add if missing company_number (registration number etc.) to… add if missing company_number (registration number etc.) to entity and customer

• Review web and UI translations

• check chatwithhal.com docs for widget company info… check chatwithhal.com docs for widget company info registration (push account data if non-white label user otherwise skip), on signup stege should be Lead, on first invoice should be Qualified, on subscribe should be Won.

• Add docs example validation system

• Improve FURS docs by splitting into logical sidebar groups

• Add llms.txt for AI-consumable documentation

• Add Documents tag for shared document operations

• Add German translations

• add api updating for properties that are normally updated… add api updating for properties that are normally updated via identify for use on servers

• Add Croatia B2C fiscalization support Add real-time B2C invoice fiscalization for Croatian businesses via the CIS (FINA) tax authority. B2C invoices from Croatian entities are reported to CIS in real-time with ZKI/JIR security codes and QR codes on PDFs. Foreign B2B invoices are allowed without fiscalization. Domestic B2B is out of scope due to strict Fiskalizacija 2.0 requirements.

• Add Hal chat widget for non-white-label users Add an in-app support chat widget for eligible authenticated users across the web app, website, and docs.

• Add entity API key creation in account Add the ability to create entity-scoped API keys (ek_*) from the /account/api-keys page. Previously this page only created account-level keys (sk_*). The embed SDK requires entity keys for security, but users had no way to create them from the account page.

Implementation

• Added optional entity selector to the create key dialog
• No entity selected → creates account key (sk_*) via POST /api-keys
• Entity selected → creates entity key (ek_*) via SDK entityApiKeys.create()
• Added "Scope" column to keys list showing "Account" or entity name
• Unified display of both key types in one view

Bug Fix

Also fixed a 404 error when creating entity API keys in /app/settings/api-keys - the page was calling /entities/{id}/api-keys but the API expects /entities/api-keys with x-entity-id header. Updated to use SDK methods which handle headers correctly.

• Fix Cloudflare Workers deployment Cloudflare wrangler-action was failing because it tried to install wrangler via npm, which doesn't support the workspace: protocol used in the monorepo. Fixed by adding packageManager: bun to all three deploy jobs in the workflow.

• Add separate Steuernummer field alongside USt-IdNr German companies have two distinct tax identifiers: the Steuernummer (local tax number from Finanzamt, varies by state) and the USt-IdNr (EU VAT ID, format DE123456789). Adding a second tax identifier field allows both to be stored and displayed on invoices — Steuernummer for domestic dealings, USt-IdNr for EU B2B. The field is generic and can serve other countries with dual tax ID systems.

• remove adding single payment on document create and allow… remove adding single payment on document create and allow adding multiple and no amounts split between equally

• add webhooks support per project for triggering events in… add webhooks support per project for triggering events in external systems

• Need to add tax rate information for different countries for… Need to add tax rate information for different countries for entities when creating to auto populate, maybe to countries data?

• some dropdown items in lists still aren't translated some dropdown items in lists still aren't translated

• Fix customer object and API spec Investigate why customer records don't have a customer object stored in the database. Also review the customer API spec/schema and compare it against similar resources (e.g. items, documents) to ensure consistency in structure and fields.

• Fix web app root route redirect Root "/" route wasn't redirecting to /account or /app. The IndexRoute component wasn't mounting due to TanStack Router behavior.

• Redesign account dashboard and fix usage charts Redesign the account dashboard entities list from bulky cards to a compact list design, and fix usage charts not rendering bars.

• Review docs important fields per endpoint

• Clean up react-ui README and remove Leka refs The published react-ui repo README has issues:

1. Contains mentions of "leka" (internal codename) that should be removed
2. Copying instructions are confusing - need to be clearer for external users

Repository: https://github.com/space-invoices/react-ui

• Publish changelog for upcoming release Review and publish the draft "Upcoming Release" changelog (ID: cml9nmhn3001f6xqv85glk55u). Currently includes the frontend SDK for embedding web app pages in iframe. Before publishing:

1. Review the draft content for accuracy and completeness
2. Add any other recently completed tasks that should be included
3. Set an appropriate version number
4. Update the title to match the release (e.g., month/year format)
5. Publish the changelog