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

# Accounts in an organization

> An organization holds any number of Buyer and Seller accounts, can create 25 accounts in any 24 hours, and holds one Developer account

## Availability

An organization has no limit on how many Buyer or Seller accounts it holds, and
no plan sets one. It can create at most 25 accounts in any 24 hours; see
[Accounts created per day](#accounts-created-per-day). Organization administrators find **Add account** in
**Settings → Organization → Accounts**; an administrator of a standalone account
finds it in **Settings → Accounts**. Adding an account never removes or archives
an existing one.

What a plan decides is which *kinds* of account the organization may hold, such
as whether it may hold both Buyer and Seller accounts. See
[Which plan holds which accounts](https://docs.apostra.com/v2/setup/account-access.md#which-plan-holds-which-accounts).
When the plan does not cover the account you add, the request is refused with
`plan_does_not_cover_account`, the plan that would, and the next step, and
nothing is created. A refusal carries `details.planSwitch`, which names the next
step (see [Errors](https://docs.apostra.com/v2/reference/errors.md#plan-gated-refusals)).

## Accounts created per day

An organization can create at most **25 accounts in any trailing 24 hours**. The
count is every Buyer, Seller and Developer account the organization created in
the last 24 hours, by any route: the **Add account** dialog,
`POST /api/v2/accounts/create-child`, `save_account` or an approved account
request. It counts creations, not the accounts that exist now, so an account
you archived or deleted after creating it still counts, and creating and
deleting accounts in a loop does not get around the limit. Restoring an
account, moving one, or converting an account into an organization is not a
creation and does not count. Repeating a creation with the same
`idempotencyKey` returns the account it already made and is never refused.

The 25th account is created and the 26th is refused. The refusal is
`429 RATE_LIMITED` with `details.reason` `account_creation_daily_limit`,
`details.limit` `25`, `details.windowHours` `24` and `details.created` (the
number already created in the window), and nothing is created. Do not retry:
the window slides, so the next account is allowed only once an earlier one is
more than 24 hours old. To raise the limit, contact support.

`save_account` (including its `dryRun` preview) and a buyer child account
request are refused with the same error when you ask, so no approval is
recorded for a creation that cannot run. An approval that reaches the limit by
the time it is approved ends as failed with the code
`account_creation_daily_limit`, and its account is not created.

Accounts that Apostra staff create for you with the staff admin tool are never
refused by this limit and do not count toward your 25, so a batch staff create
for you never blocks your own creations. The exemption is that tool only: a
Apostra staff member who creates an account through the same routes you use
(`POST /api/v2/accounts/create-child` or `save_account`) is limited like
anyone else, and that creation counts.

Archiving and restoring an account follow the same rule. Archived accounts
retain their history. Restoring one is refused only when the plan no longer
covers it, or when it is a Developer account and the organization already has
another.

Advertisers and connected advertising-platform accounts are not accounts of the
organization and do not count toward it.

## The Developer account

An organization holds one Developer account, and it can hold any number of
agents. Every plan covers it. Create it from the organization's **Accounts**
screen or with `save_account`. A second Developer account is refused with
`409 CONFLICT` and `details.resource` `developer_account_limit`, and nothing
changes: build further agents in the existing Developer account. Holding agents
you operate on behalf of other companies is part of the Certified Agent
Partner Program.

When creating an eligible Buyer account, **Operator domain** means the domain
of the organization operating that account. For a Seller account, **Company
domain** means the company operating the storefront; it initially seeds the
operator domain and remains separate from the storefront's public listing domain.

For the API operation, see the Buyer or Storefront
`POST /api/v2/accounts/create-child` reference.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.