Choose Your Path

Start With The Integration You Actually Need

The fastest way to get value from Space Invoices depends less on industry and more on how much UI, backend control, and tenant isolation you need.

Use this page to choose the right path before you read implementation details.

Path	Best for	Time to first value	UI ownership	Backend required	Recommended next page
JavaScript SDK	Custom product flows, backend automation, full control	Half day to 2 days	Full	Yes	JavaScript SDK
Embed SDK	Fastest route to working invoicing UI	A few hours	Low	Usually yes	Embed SDK
React UI	React teams that want real component ownership	1 to 3 days	High	Yes	React UI
Direct API only	Non-JS stacks or teams building their own client	1 to 3 days	Full	Yes	API Reference

Use JavaScript SDK If

• you want typed backend workflows for invoices, customers, items, payments, or exports
• you need your own UI or no UI at all
• you want the simplest path from sandbox proof-of-concept to production rollout

Not ideal if you want a ready-made invoicing interface this week.

Next:

• JavaScript SDK
• Quickstart

Use Embed SDK If

• you want pre-built invoicing screens without owning frontend component code
• you need the shortest path to an embedded UI in an existing app
• you can work with iframe-based integration boundaries

Not ideal if you need deep DOM-level customization or want to fold components directly into your design system.

Next:

• Embed SDK
• User Access

Use React UI If

• you are already shipping React
• you want copy-paste components you can fully own and modify
• you need more flexibility than an embed without building every screen from scratch

Not ideal if your team is not on React or you want a zero-maintenance UI surface.

Next:

• React UI
• Provider Setup

Use Direct API Only If

• you are on another backend stack
• you want to call the raw REST API without SDK abstractions
• you need total control over transport, auth, and client generation

Not ideal if you are optimizing for the fastest path and are already comfortable with TypeScript.

Next:

• API Reference
• Authentication

Choose By Product Shape

If your product looks like this	Start here
One business, one issuing entity	Quickstart
One platform, many customer businesses	Multi-Tenancy
You need end-user dashboard access	User Access
You want the docs mapped to your market	Use Cases

Recommended default

If you are unsure, start with the JavaScript SDK and a sandbox entity. It gives the clearest path from proof-of-concept to production and keeps your future options open.

What The First Week Usually Looks Like

1. Sign up and create a sandbox entity.
2. Generate the right key type for your path.
3. Issue one sandbox invoice.
4. Confirm rendering, tax behavior, and delivery flow.
5. Decide how your end users will access invoicing, if applicable.

Next Steps

• Introduction — confirm the product model
• Quickstart — create the first invoice
• Use Cases — match the docs to your architecture