# Register user with password

> **Legacy.** This endpoint is kept for existing integrations. Use the current API reference for new work.

This page documents `POST /auth/register`.

- Endpoint: `POST https://api.returning.ai/auth/register`
- Section: Legacy / Authentication
- Authentication: `Authorization: Bearer <API_KEY>` (Community API key)
- Retries: Repeating register will not mount the route.
- Guide: generated from the published specification
- Last updated: 26 Sep 2026
- Web page: https://docs.returning.ai/api-reference/legacy-authentication/register-user-with-password

## Authentication

- Header: `Authorization: Bearer <API_KEY>`

This is not a community API-key route. A valid integration key does not register a password account here.

## Behaviour

That register route is **not mounted** on `https://api.returning.ai`.

Do not use it to provision broker members. Use [Create New User](https://docs.returning.ai/api-reference/users/create-user.md).

**Replacement:** `POST /v1/users` with a community API key that includes `createUser`.

## Request

### Headers

| Name | Type | Required | Description |
| --- | --- | --- | --- |
| `Authorization` | `string` | Yes | API key. (`Bearer <API_KEY>`) |
| `Content-Type` | `string` | Yes | Request body format. (`application/json`) |

### Body

| Name | Type | Required | Description |
| --- | --- | --- | --- |
| `email` | `string` | Yes | Email address for the new user. (Email format) |
| `password` | `string` | Yes | Password for the new account. |
| `name` | `string` | No | Optional display name for the user. |

### Watch for

- Password register is Legacy Authentication, not broker ingestion.
- Login on the same host also 404s (`Cannot POST /api/secureAuth/login` when called as `/v1/auth/login`).

### Example request

```bash
curl --request POST \
  --url https://api.returning.ai/auth/register \
  --header 'Authorization: Bearer <API_KEY>' \
  --header 'Content-Type: application/json' \
  --data '{
    "email": "user@example.com",
    "password": "StrongPassword123!",
    "name": "Test User"
  }'
```

### More examples

There is no success example. `POST /auth/register` returns `404`.

## Response

No success response on this gateway. Readback for created members is `POST /v1/users/info`.

### Response fields

| Field | Type | Presence | Description |
| --- | --- | --- | --- |
| `status` | `string` | - | - |
| `data` | `object` | - | - |

### Example response (200)

```json
{
  "status": "success"
}
```

## Errors

### Fix the request

| Status | Code | What to do |
| --- | --- | --- |
| 400 | - | The request body is missing required fields or contains invalid email/password values. |
| 401 | - | Authentication context is invalid or the endpoint is not enabled for the current application. |

### Fix the data

| Status | Code | What to do |
| --- | --- | --- |
| 409 | - | A user with the same email already exists. |

### Retry with backoff

| Status | Code | What to do |
| --- | --- | --- |
| 500 | - | Unexpected server error. |

**Retries:** Repeating register will not mount the route.

## Next step

- [Create New User](https://docs.returning.ai/api-reference/users/create-user.md): `POST /v1/users`. Provision the member with the community API key.