Claim flow

Hand a project you created over to your customer: a claim link moves it into their own StitchDB organization with its data, URL and keys.

Build an app for a customer, then let them take it over:

Terminal

curl -X POST https://stitchdb.com/platform/v1/projects/<ref>/claim-links \
  -H "Authorization: Bearer $STITCHDB_TOKEN" -H 'Content-Type: application/json' \
  -d '{ "expires_in_days": 7, "keep_role": "developer" }'

Send the returned url to your customer. They sign in (or sign up for free) and choose the organization to claim it into (one they own or administer). Then:

The project, its preview branches, data, URL and API keys move to their organization; their plan, limits and billing apply. Your labels, caps and expiry are removed.
You lose access, unless you asked to keep_role (admin, developer or read_only), which gives your account that role on this one project only.
Both organizations receive project.claimed.

Links are single-use, expire (1-30 days) and can be revoked with DELETE /projects/<ref>/claim-links/<id>. Claiming needs room in the customer's plan; projects with read replicas cannot be claimed until they are removed.