Set up your account

Do this before you write a line of integration code. It takes about ten minutes, and everything here happens in test mode — an isolated environment that is free, never billed, and never moves real money.

Organizations and apps

Invitebase is organized in two levels:

• Organization — your company. Members, billing, and API access are org-scoped. You invite teammates by email from Settings.
• App — a product inside the organization (for example, your iOS/Android/web app). Campaigns, users, events, keys, and analytics all belong to an app. Use the app switcher in the top bar to move between apps.

Most teams have one app per product. Create additional apps only when you run separate products with separate referral campaigns, users, and keys. For the full tour of every section, see the dashboard overview.

Create your organization and first app

Sign up at invitebase.com/signup. Creating your account creates your organization and your first app in one step. It will walk you through the Get started checklist.

The checklist is auto-detecting: it walks you from signup to a first validated referral, and each step checks itself off the moment Invitebase observes the signal server-side — you never mark anything done by hand. See the Get started checklist for what each step detects.

Grab your test API keys

Open Developers → API keys in the dashboard. Every app has two key types, and the prefix tells you the mode at a glance:

• Public (pk_test_…) — for client-side SDKs. Safe to ship in your app.
• Secret (sk_test_…) — for server-side calls. Keep it on your backend only.

The _test_ prefix is what puts you in test mode; there is no separate sandbox host — the key alone determines the environment. Reveal and copy your test keys now, since you will paste them into the SDK next.

For creating, rolling, and revoking keys, see Developer tools and the API keys guide. For how test and live are separated, see Environments and test mode.

Invite your team

Members are org-scoped, so a teammate you invite can work across every app in the organization. Invite them by email from Settings — that page covers member management alongside your app and notification settings.

Configure your app

A little configuration up front makes the SDK integration smoother:

• App name and subdomain — set in Settings → General. Every app gets a refr.link subdomain, chosen when you create the app.
• Attribution — in Settings → Attribution, enter the values that let your referral links open your app: your Apple Team ID and bundle ID for iOS, and your Android package name and SHA-256 signing-certificate fingerprints. These are the same values the SDK setup steps reference.

You can do this now or when you reach the SDK's link-handling step. See Settings for the full reference and Deep links for the SDK side of Universal Links and Android App Links.

What's next

Your account is ready. The next two steps are product decisions you make in the dashboard — no code yet — before you integrate:

In a hurry, or want to see code first? Install with AI wires the SDK, your keys, and a first campaign into your codebase from a single pasted prompt — or jump straight to the platform quickstarts.