> ## Documentation Index
> Fetch the complete documentation index at: https://docs.digitalseaservice.com/llms.txt
> Use this file to discover all available pages before exploring further.

# account_requires_signup

> HTTP 409 — this email does not have a Digital Sea Service account yet.

<Note>
  **Partner-restricted.** Only returned by the
  [Sponsorship API](/sponsorships/overview), which requires a sponsorship program.
</Note>

```http theme={null}
HTTP/1.1 409 Conflict
Content-Type: application/problem+json
X-Request-Id: req_01HV9XK...

{
  "type": "https://docs.digitalseaservice.com/errors/account_requires_signup",
  "title": "DSS account required",
  "status": 409,
  "detail": "This email does not have a Digital Sea Service account yet. Send the member to signup_url to create one, then Connect.",
  "instance": "req_01HV9XK...",
  "signup_url": "https://app.digitalseaservice.com/signin?intent=signup&partner=ywc&email=jane%40example.com&first_name=Jane&last_name=Doe"
}
```

## What it means

You called [`POST /v1/partners/sponsorships`](/sponsorships/provision) for an
email that is **not yet a DSS member**. We no longer create a passwordless
account or send a “set your password” email. The member must complete **normal
DSS signup** (password + verify-email), then Connect. Premium is granted on
Connect.

## What to do

1. Redirect the member’s browser to `signup_url` (or build the same URL
   yourself — see [Set up a DSS account](/sponsorships/sso#set-up-a-dss-account)).
2. After they verify email, run your existing **Connect** flow.
3. Call `POST /v1/partners/sponsorships` again only once they already have a
   DSS account (or rely on entitle-on-Connect).

Do not treat this as unreachable. It is a setup step.

## Related

* [Open DSS (YWC SSO)](/sponsorships/sso)
* [Provision a seat](/sponsorships/provision)