# What the sign-up page asked before there was one way in

> tidekeeper's API reference: https://tidekeeper.eu/docs/api/post-auth-signup

`POST /api/v1/auth/signup`

What the sign-up page asked before there was one way in: now the same as Continue, whatever else it carries.

## What to send

`SignupStart`

- `accept` (boolean): The terms and the data processing agreement, where this deployment publishes either; where it publishes neither, nothing is asked.
- `account` (string or null): What the account is called. Without one it is called after its first site, and without that after the address.
- `email` (string, needed)
- `how` (string): `password`, `link` or `passkey`: how they mean to sign in.
- `password` (string or null)
- `site` (string or null): A first site, by its domain.

## The answer

202, `Sent`: The same answer whoever asked and whatever was found: a page that sends a link cannot be used to learn who has an account.

- `again_in` (integer, needed): How long before another can be asked for, in seconds.
- `minutes` (integer, needed): How long the link works, in minutes.
- `sent` (boolean, needed)

## Asking

```sh
curl -X POST https://tidekeeper.eu/api/v1/auth/signup \
    -H "Authorization: Bearer $TIDEKEEPER_TOKEN" \
    -H "Content-Type: application/json" \
    -d '{"email": "…"}'
```