# Create an account for a verified wallet and sign in

Called with the hosted sign-in context, using the signupToken from wallet verification (401 once it has expired or after three tries).

`POST /api/v1/auth/wallet/register`

- Sign-in: No credential. Name the organization with the hosted sign-in state header or the org query parameter.
- Rate limit: Up to 500 requests every 3 seconds per IP address; up to 1,000 requests a minute per API key (some requests are not counted); up to 10 requests a minute per IP address.

Called with the hosted sign-in context, using the `signupToken` from wallet verification (401 once it has expired or after three tries). Creates the account with the given email, links the wallet, then answers a login token or a second-step challenge. Answers 409 when the email cannot be used, 403 when sign-up is closed, and 400 for a disposable address.

## Request

Send the body as `application/json`.

| Field              | Type   | Required | Constraints                            | Description |
| ------------------ | ------ | -------- | -------------------------------------- | ----------- |
| `signupToken`      | string | Yes      | 40 to 40 characters                    | -           |
| `name`             | string | Yes      | 1 to 200 characters                    | -           |
| `email`            | string | Yes      | format `email`, at most 320 characters | -           |
| `turnstileToken`   | string | No       | at most 2048 characters                | -           |
| `captchaToken`     | string | No       | at most 8192 characters                | -           |
| `context`          | object | No       | -                                      | -           |
| `context.timezone` | string | No       | at most 64 characters                  | -           |
| `context.country`  | string | No       | at most 64 characters                  | -           |
| `context.language` | string | No       | at most 64 characters                  | -           |
| `context.currency` | string | No       | at most 64 characters                  | -           |

## Example request

Replace each `YOUR_...` value with your own.

```bash title="cURL"
curl -X POST "https://api.console.buildbase.app/api/v1/auth/wallet/register?org=YOUR_ORG_ID" \
  -H "Content-Type: application/json" \
  -d '{
  "signupToken": "string",
  "name": "Example",
  "email": "user@example.com"
}'
```

```ts title="TypeScript"
const response = await fetch(
  'https://api.console.buildbase.app/api/v1/auth/wallet/register?org=YOUR_ORG_ID',
  {
    method: 'POST',
    headers: {
      'Content-Type': 'application/json',
    },
    body: JSON.stringify({
      signupToken: 'string',
      name: 'Example',
      email: 'user@example.com',
    }),
  }
);
if (!response.ok) {
  throw new Error(`${response.status}: ${await response.text()}`);
}
const data = await response.json();
```

```python title="Python"
import requests

response = requests.post(
    "https://api.console.buildbase.app/api/v1/auth/wallet/register?org=YOUR_ORG_ID",
    json={
        "signupToken": "string",
        "name": "Example",
        "email": "user@example.com",
    },
    timeout=30,
)
response.raise_for_status()
data = response.json()
```

## Responses

### 200 OK

OK

```json title="Example"
{
  "data": {
    "deviceToken": "[REDACTED]",
    "token": "[REDACTED]",
    "user": {
      "name": "Wallet Person",
      "role": "user"
    }
  },
  "success": true
}
```

### Any other status

Any other answer the handler sends itself (its own refusals). Not described yet.

## Errors

Each refusal, what it means, and what to do. The request changed nothing.

### 400 Bad Request

**What it means:** The request failed a `validate()` schema, or an id in the path is not a valid id. `path` names the field.

**What to do:** Fix the field the body names in `path` (or read `message`) and send the request again. Nothing was changed.

```json title="Example"
{
  "error": true,
  "success": false,
  "path": "string",
  "message": "string"
}
```

### 401 Unauthorized

**What it means:** The credential is missing, expired or not accepted here, or the caller's role has no grant for `x-permission` (refused with 401 too). The body is the plain text `Unauthorized`, or a JSON body with a `code` where the gate says why.

**What to do:** Send the credential this operation asks for (see Sign-in above), or sign in again if it expired. A valid credential is also refused when the role has no grant for the permission above.

```text title="Example"
Unauthorized
```

### 429 Too Many Requests

**What it means:** A rate limit in `x-rateLimit` was reached. `retryAfter` and the `Retry-After` header say how many seconds until the window resets.

**What to do:** Wait the number of seconds in the `Retry-After` header (also `retryAfter` in the body), then retry. Slow down repeated calls.

```json title="Example"
{
  "success": false,
  "message": "string",
  "reason": "rate_limited",
  "retryAfter": 1
}
```

## Events

A successful call can send these [webhook events](/webhooks/overview) to the endpoints that subscribe to them:

- [`user.registered`](/webhooks/overview#when-each-event-fires)
- [`user.account_linked`](/webhooks/overview#when-each-event-fires)
- [`user.logged_in`](/webhooks/overview#when-each-event-fires)

## Related

- [Auth guide](/authentication/overview): how this part of BuildBase works
- [All Auth operations](/http-api/reference/auth)
- [API reference](/http-api/reference): every operation, by tag
- [Sign-in and credentials for the HTTP API](/http-api/authentication)
- [How the HTTP API reports errors](/http-api/errors)
- [Make your first call](/http-api/first-call)
- [Error codes](/reference/error-codes): every `code` the API returns
- OpenAPI: operation `auth.wallet.register.create` in [public-v1.json](https://docs.buildbase.app/openapi/public-v1.json)
