Multi-Project Setup

Windback supports managing churn recovery for multiple products from a single account. Each project gets its own API keys, payment provider connections, churn events, and allowed origins.

How It Works

Projects are the top-level organizational unit in Windback. When you create an account and complete onboarding, a Default project is created automatically. You can then create additional projects for each of your SaaS products.

Each project is completely isolated:

• Separate API keys (public + secret)
• Independent Stripe / Razorpay connections
• Scoped churn events and recovery stats
• Per-project allowed origins for the widget
• Unique slug used in URLs and API paths

Creating a Project

Via Dashboard

1. Go to Projects in the sidebar
2. Click Create Project
3. Fill in the project details:
   • Name — Your product name (e.g. "Acme Pro")
   • Product Type — The type of SaaS product
   • Support Email — Email shown in recovery emails
4. A URL-friendly slug is generated automatically from the name

Via API

curl -X POST https://api.windback.dev/api/v1/projects \
  -H "Authorization: Bearer <token>" \
  -H "Content-Type: application/json" \
  -d '{
    "name": "Acme Pro",
    "product_type": "SaaS",
    "support_email": "support@acme.com"
  }'

Response:

{
  "data": {
    "id": "550e8400-e29b-41d4-a716-446655440000",
    "name": "Acme Pro",
    "slug": "acme-pro",
    "product_type": "SaaS",
    "support_email": "support@acme.com",
    "allowed_origins": [],
    "created_at": "2026-02-17T10:00:00Z",
    "updated_at": "2026-02-17T10:00:00Z"
  }
}

Project-Scoped API

All core endpoints are scoped under a project slug:

https://api.windback.dev/api/v1/projects/{slug}/...

Switching Between Projects

In the dashboard, use the project switcher in the sidebar to navigate between your projects. Each project has its own overview, events list, and settings pages.

Dashboard URLs follow the pattern:

/dashboard/p/{slug}/          → Project overview
/dashboard/p/{slug}/events    → Churn events
/dashboard/p/{slug}/settings  → Project settings

Connecting Payment Providers

Each project connects to its own payment provider accounts. Go to Settings > Integrations within a project to configure:

• Stripe — Enter your Stripe account ID
• Razorpay — Enter your Razorpay key ID

Webhook URLs are project-scoped via the project's public API key:

https://api.windback.dev/api/v1/webhooks/stripe/{project_public_key}
https://api.windback.dev/api/v1/webhooks/razorpay/{project_public_key}

Managing API Keys

Each project has its own key pair:

View your project's API keys at Settings > API Keys within the project.

Allowed Origins

Configure per-project CORS origins to control which domains can use the cancellation widget:

curl -X PUT \
  https://api.windback.dev/api/v1/projects/acme-pro/allowed-origins \
  -H "Authorization: Bearer <token>" \
  -H "Content-Type: application/json" \
  -d '{"allowed_origins": ["https://acme.com", "https://staging.acme.com"]}'

Updating a Project

curl -X PUT https://api.windback.dev/api/v1/projects/acme-pro \
  -H "Authorization: Bearer <token>" \
  -H "Content-Type: application/json" \
  -d '{
    "name": "Acme Pro",
    "product_type": "SaaS",
    "support_email": "help@acme.com"
  }'

Deleting a Project

curl -X DELETE https://api.windback.dev/api/v1/projects/acme-pro \
  -H "Authorization: Bearer <token>"

Slug Uniqueness

Project slugs are unique per user, not globally. If a slug collision is detected within your account, a short UUID suffix is appended automatically (e.g. acme-pro-a1b2c3).

Next Steps

• Authentication — Understand JWT and API key auth
• API Reference — Full endpoint reference
• Stripe Integration — Connect Stripe to a project
• Widget Installation — Add the cancellation widget