---
search:
  tags:
    - Portfolio
    - POST
seo:
  description: >-
    Creates an account for the caller's member and starts its asynchronous
    setup. An API… Reference for the POST /portfolio/accounts endpoint in the
    REST API API.
sidebar:
  badge: POST
  label: Create an Account
title: Create an Account
type: openapi-operation
---
Creates an account for the caller's member and starts its asynchronous setup. An API key must be unrestricted and carry the trade scope; an account-restricted key cannot create an account. A member without an active clearing arrangement is rejected without creating an account.

### Endpoint

- Method and path: `POST /portfolio/accounts`
- Operation ID: `createAccount`
- API reference: [POST /portfolio/accounts](/api-reference/portfolio/createaccount)

#### Authorization

- Accepted credentials: `UDX-Access-Key` header and `UDX-Access-Timestamp` header and `UDX-Access-Signature` header; or Bearer token in `Authorization`
- Details: [Authentication](/authentication)

#### Parameters

- `UDX-Version` (`header`) — Dated API version (YYYY-MM-DD). Omit to use the oldest supported version. An unknown version returns `400`.
- `UDX-Idempotency-Key` (`header`) — Optional client-generated key that makes a mutation safe to retry. Reuse it only for a byte-identical retry. When present, it is included in the request signature; omitting it disables UDX idempotency for that request.

#### Request body

- Content type: `application/json`
- Schema: `CreateAccountRequest`
- Required: yes
- Fields:
  - `name` (string, required) — Human-readable name for the account.

#### Responses

- `202` — The account was created and its asynchronous setup started. It begins in the pending state. Poll GET /portfolio/accounts with the same authenticated credential until it becomes active. UDX retries failed setup; keep polling a failed account and contact UDX support if it persists. When supplied, reusing the creation idempotency key only replays this response and does not create or repair another account.
- `400` — The request doesn't conform to this spec.
- `401` — No valid credential was provided.
- `403` — The credential lacks the `trade` scope or is restricted to one account.
- `409` — This key is still in use or its response cannot be replayed. The mutation may have run; check `detail` before retrying.
- `422` — This key belongs to a different request.
- `429` — The Member's request rate is exhausted. Wait for `Retry-After`.
- `500` — Something went wrong on UDX's side.
- `503` — Request admission is unavailable. Retry later.