SnozeDevelopers
API referenceOnboarding

Accept a legacy workspace restore claim

Claims the restored workspace behind an offer for the caller and returns the resulting workspace summary. Requires a Clerk session whose verified email matches the claim, checked without the profile cache, and the legacy-restore feature must be enabled. An unknown, blocked, or non-matching claim is not found; a workspace that is not activated yet, an offer already resolved, and a legacy identity already claimed by another account are all conflicts. Re-accepting a claim the caller already accepted returns the same workspace.

POST
/v1/me/legacy-workspace-claims/{claimId}/accept

Authorization

apiKey
headerAuthorizationBearer <snoze_sk_…>

Workspace API key created in Workspace settings → API keys. Scopes on the key bound what it can read and write.

Path Parameters

claimId*string

Response Body

Success

application/json
  1. response
data*
Example Request
curl -X POST 'https://api.snoze.dev/v1/me/legacy-workspace-claims/string/accept'
Example Response
{  "data": {    "claimId": "string",    "workspace": {      "id": "string",      "slug": "string",      "name": "string",      "icon": "initials",      "accentColor": "string",      "imageUrl": "string",      "role": "owner",      "seatStatus": "active",      "permissions": [        "workspace:read"      ],      "createdAt": "string",      "updatedAt": "string"    }  }}

List the workspace offers waiting for the caller

Returns the caller's pending workspace invites and, when the legacy-restore feature is enabled for them, the legacy workspace claims matched to their verified email address, ordered for the onboarding screen. Any authenticated caller with a synced profile may read their own offers; a caller with no verified email gets an empty list. Listing a stale offer is harmless, because accepting one re-checks strictly and rejects.

Skip a legacy workspace restore claim

Declines an offered restore and reports the outcome: dismissed, the workspace deleted, or ownership transferred to another legacy member. Requires a Clerk session whose verified email matches the claim. An unknown or non-matching claim is not found and an offer already resolved another way is a conflict; skipping one that was already skipped or deleted returns the recorded outcome again.