Skip to content

`POST /v1/auth/sign-up`.

POST
/v1/auth/sign-up
curl --request POST \
--url https://api.updawg.net/v1/auth/sign-up \
--header 'Content-Type: application/json' \
--data '{ "email": "example", "name": "example", "organization": "example" }'
Media typeapplication/json
object
email
required
string
name
required

The person’s name, as their colleagues will see it.

string
organization
required

The organization’s name. Its slug is derived from it, and can be changed later in Settings.

string

Example generated

{
"email": "example",
"name": "example",
"organization": "example"
}

Accepted: a mail is on its way. ⚠️ The same answer whether or not the address already has an account — one that has is sent a sign-in link instead.

Not an address, or a name missing or too long.

Media typeapplication/json
object
detail
string | null
status
required
integer format: int32
title
required
string
type
required
string

Example generated

{
"detail": "example",
"status": 1,
"title": "example",
"type": "example"
}

The address’s domain belongs to an organization that requires single sign-on: sso-required. About the domain, not the person (DAWG-155). Or this deployment does not let people make their own accounts: sign-up-closed.

Media typeapplication/json
object
detail
string | null
status
required
integer format: int32
title
required
string
type
required
string

Example generated

{
"detail": "example",
"status": 1,
"title": "example",
"type": "example"
}

Too many links asked for this address, or from this source.

Media typeapplication/json
object
detail
string | null
status
required
integer format: int32
title
required
string
type
required
string

Example generated

{
"detail": "example",
"status": 1,
"title": "example",
"type": "example"
}