> ## Documentation Index
> Fetch the complete documentation index at: https://docs.annature.com.au/llms.txt
> Use this file to discover all available pages before exploring further.

# Create an account

Creates a new account that can be used to log in to the Annature dashboard and send, sign, or manage envelopes.

By default, newly created accounts will receive a verification email from Annature prompting them to set a password. Until verified, accounts cannot log in or send envelopes.

Optionally, a password can be provided in the request to set it programmatically. This is useful when provisioning internal users or simplifying onboarding. If no password is provided, the user will need to set it manually via the verification email.

Verification emails can be resent using the [Resend verification](/api-reference/accounts/resend-verification) endpoint.

### Partner-specific behavior

If you're part of the [Partner Program](/api-reference/partner-program) and supply the `X-Annature-Partner` header, you may include a `skip_verification` flag in the request to bypass the standard email verification process.

This allows accounts to be created in a pre-verified state — for example, when programmatically provisioning known users or performing a controlled migration.

## Parameters

<ParamField path="name" type="string" required>
  The full name of the account holder.
</ParamField>

<ParamField path="email" type="string" required>
  The email address associated with the account. This will be used to log in to the Annature dashboard.

  Email addresses must be unique. An error will be returned if the supplied email already exists for another account.
</ParamField>

<ParamField path="password" type="string">
  Set the password for the account at the time of creation. If omitted, the user will be asked to set their password via the email verification link.
</ParamField>

<ParamField path="number" type="string">
  The account holder’s contact number.
</ParamField>

<ParamField path="timezone" type="string">
  The timezone assigned to this account, supplied as a 6-digit UTC offset.

  Timezones must be supplied as a 6-digit UTC offset. For example:

  * `+10:00` → Australia/Brisbane
  * `+08:00` → Australia/Perth
</ParamField>

<ParamField path="role" type="string">
  The account role. If not specified, the account will default to `standard`.

  Possible values: `administrator`, `standard`, `read-only`.
</ParamField>

<ParamField path="group_id" type="string">
  The unique identifier of the [group](/api-reference/groups/group-object) this account should be assigned to.
</ParamField>

<ParamField path="skip_verification" type="boolean">
  **Partner-only**: Set this to `true` to mark the account as verified without sending an email. Requires the `X-Annature-Partner` header.
</ParamField>

<RequestExample>
  ```bash Endpoint theme={null}
  POST /v1/accounts
  ```

  ```json Body theme={null}
  {
    "name": "Ted Annature",
    "email": "ted@annature.com.au",
    "password": "secret123",
    "number": "1300 000 000",
    "timezone": "+10:00",
    "role": "administrator",
    "group_id": "a5a885caee6286a54ad7bbd4ab5400e9",
    "skip_verification": true
  }
  ```
</RequestExample>

<ResponseExample>
  ```json Response theme={null}
  {
    "id": "c64ce66b70b21c03bfd5dfa0ab14b730",
    "name": "Ted Annature",
    "email": "ted@annature.com.au",
    "number": "1300 000 000",
    "timezone": "+10:00",
    "role": "administrator",
    "active": true,
    "organisation_id": "62e9a87c6ed1444d9d228c4a0374017d",
    "group_id": "a5a885caee6286a54ad7bbd4ab5400e9",
    "created": "2019-12-17T05:30:00Z",
    "verified": "2019-12-17T05:30:00Z"
  }
  ```
</ResponseExample>
