Skip to content
Space Invoices Documentation

Introduction

Space Invoices is an API-first invoicing platform for products that need compliant documents, PDFs, tax-aware calculations, and multi-tenant separation without building the whole invoicing stack in-house. The value is not just invoice creation. It is the compliance, access, and operational surface area behind it.

Who This Is For

Use Space Invoices when you are:

  • adding invoicing to a SaaS, fintech, marketplace, store, or internal back-office tool
  • serving one business now but want a clean path to multiple entities later
  • deciding between direct API control, typed SDKs, embedded UI, or copy-paste React components
  • trying to validate the product quickly in sandbox before touching live customers

When This Is Probably Not The Right Tool

Skip this route if:

  • you only need a local invoicing app for one human operator and no integration surface
  • you want a no-code website builder rather than an API and developer workflow
  • you are looking for a generic billing subscription engine instead of document issuance and compliance infrastructure

What You Actually Get

  • entity-scoped data isolation
  • invoices, estimates, delivery notes, credit notes, payments, and related resources
  • sandbox and live environments with separate keys and data
  • PDF and HTML rendering
  • country-aware tax and compliance behavior
  • multiple frontend paths: API, JavaScript SDK, Embed SDK, React UI

Why Teams Buy Instead Of Build

AI can make invoice CRUD, templates, and scaffolding faster to produce. It does not remove the cost of:

  • country-specific compliance rules
  • fiscalization and e-invoicing workflows
  • entity-per-customer or entity-per-seller isolation
  • auditability, corrections, exports, and support operations after launch

The Real Signup-To-First-Value Flow

The common onboarding path is:

  1. Sign up for a free account
  2. Create your first entity
  3. Generate the right API key for sandbox or live
  4. Create your first invoice
  5. Render or send it

New signups do not arrive with a ready-to-use default entity. The first entity is created after signup.

API Structure

Resource-based REST. Most data operations are scoped to an entity. Account-level operations manage entities and higher-level access.

Multi-Tenancy Model

Multi-tenancy structure
┌───────────────────────────────────────────┐
│              Your Platform                │
│         (Account-level API key)           │
└───────────────────┬───────────────────────┘
                    │
      ┌─────────────┼─────────────┐
      │             │             │
      ▼             ▼             ▼
┌───────────┐ ┌───────────┐ ┌───────────┐
│  Entity A │ │  Entity B │ │  Entity C │
├───────────┤ ├───────────┤ ├───────────┤
│ • Data    │ │ • Data    │ │ • Data    │
│ • Config  │ │ • Config  │ │ • Config  │
│ • Users   │ │ • Users   │ │ • Users   │
└───────────┘ └───────────┘ └───────────┘

Each entity is isolated with its own data and settings.

That means the same platform works for:

  • one issuing business
  • one platform with many customer businesses
  • one marketplace with many seller entities
  • one accounting team managing many clients

Sandbox First

Start in sandbox whenever you are still validating flows, examples, or compliance behavior.

Sandbox gives you:

  • separate keys
  • separate entities
  • no risk of creating live documents
  • the same API model you will use in production

Quick Example

Create an invoicetypescript
import SpaceInvoices from "@spaceinvoices/js-sdk";

const sdk = new SpaceInvoices("YOUR_API_KEY");

const _invoice = await sdk.invoices.create({
  customer: { name: "Acme Corp", email: "billing@acme.com" },
  items: [{ name: "Web Development", quantity: 1, price: 2500 }],
});

Choose Your Integration Path

Use the Choose Your Path guide if you need help deciding between:

  • JavaScript SDK
  • Embed SDK
  • React UI
  • direct REST API

Next Steps