MEMBER_ALREADY_IN_ACCOUNT
That person is already a member of the account.
Category: Accounts
| HTTP status | 409 Conflict |
| Retry | No |
When it happens
The email already belongs to a member of this account, so there is nobody to invite.
Retry
Do not retry. The outcome is final: sending the same request again gets the same answer.
Example response
When this error occurs, the API answers 409 Conflict with a JSON body of this shape:
{
"type": "https://docs.beel.es/errors/MEMBER_ALREADY_IN_ACCOUNT",
"title": "MEMBER_ALREADY_IN_ACCOUNT",
"detail": "That person is already a member of the account.",
"instance": "/v1/<resource>",
"errors": [],
"success": false,
"error": {
"code": "MEMBER_ALREADY_IN_ACCOUNT",
"message": "That person is already a member of the account.",
"details": {}
},
"meta": {
"timestamp": "2026-05-21T10:00:00Z",
"request_id": "4bf92f3577b34da6a3ce929d0e0e4736"
}
}The type URI is stable and always resolves to this page.
Message
Send the request with Accept-Language: <es|en|ca> to receive the message in your preferred language.
Other errors in this category
CLAIM_TOKEN_EMAIL_REQUIRED
The account has no holder yet: send the email of the person who will claim it.
CLAIM_TOKEN_HOLDER_MISMATCH
That account already has a holder with a different email. Omit the field to re-issue the link to them.
DISPLAY_NAME_BLANK
The account name must not be blank.
GRANT_ACCESS_LEVEL_INVALID
A grant's access level must be VIEW or OPERATE. To remove access to a company, omit it from the set.
GRANT_COMPANY_NOT_IN_ACCOUNT
One of the specified companies does not belong to this account.