---
"@context": https://schema.org
"@type": TechArticle
"@id": https://www.twilio.com/docs/api/errors/21100#article
headline: "21100: Accounts Resource"
url: https://www.twilio.com/docs/api/errors/21100
inLanguage: en
dateModified: 2026-06-09T11:00:42.000Z
author:
  "@type": Organization
  name: Twilio Developer Education Team
publisher:
  "@type": Organization
  name: Twilio
---

# 21100: Accounts Resource

Log Level: ERROR

## Description

This error indicates that a request to the Accounts resource could not be completed. Review the request path, authentication context, and any values you send for account properties such as `FriendlyName` or `Status` before retrying.

### Possible causes

* The request used an invalid Account SID in the path. Account SIDs for this resource must match the `AC` SID format and identify the account you want to fetch or update.
* The request included an invalid value for `Status`. The Accounts resource only accepts `active`, `suspended`, or `closed`.
* The request used credentials that do not have access to the target account. Subaccount credentials cannot access the main account or other subaccounts.
* The request used a main account API Key to access subaccount resources. Main account API Keys only grant access to main account resources.
* The request attempted to update an account in a way the resource does not allow, such as closing the main account or trying to reopen a closed subaccount.
* The request included an invalid `FriendlyName`, such as a value that exceeds the allowed length for the account resource.

### Possible solutions

* Confirm that the request targets the correct Accounts endpoint, such as `/2010-04-01/Accounts.json` for creating a subaccount or `/2010-04-01/Accounts/{Sid}.json` for fetching or updating an account.
* Verify that the `Sid` in the request path is a valid Account SID and belongs to the account you intend to manage.
* Send only supported values for `Status`: `active`, `suspended`, or `closed`.
* Use the correct credentials for the operation. For work inside a subaccount, use the subaccount SID and Auth Token or subaccount-level API Keys where supported.
* Use main account credentials when you need to close a subaccount. Do not try to close your main account.
* Verify the `FriendlyName` value and keep it within the limits supported by the Accounts resource.
* If you are creating subaccounts, create them from the main account that will own them and verify that your account is allowed to create additional subaccounts.

#### Additional resources

* [REST API: Accounts](/docs/iam/api/account)
* [REST API: Subaccounts](/docs/iam/api/subaccounts)
* [Our API: the basics](/docs/iam/api)