CONNECTION_DUPLICATE
The company already has a connection with this provider.
Category: Connections
| HTTP status | 409 Conflict |
| Retry | No |
When it happens
The provider allows one live connection per company and environment, and the company already has it; error.details.connection_id is its id.
How to fix it
Use the existing connection, or disconnect it first to create a new one.
Retry
Do not retry. The outcome is final: sending the same request again gets the same answer.
Returned by
The operations where this code is most likely. The list is not exhaustive.
Example response
When this error occurs, the API answers 409 Conflict with a JSON body of this shape:
{
"type": "https://docs.beel.es/errors/CONNECTION_DUPLICATE",
"title": "CONNECTION_DUPLICATE",
"detail": "The company already has a connection with this provider.",
"instance": "/v1/<resource>",
"errors": [],
"success": false,
"error": {
"code": "CONNECTION_DUPLICATE",
"message": "The company already has a connection with this provider.",
"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
COMPANY_CONNECTION_NOT_FOUND
Connection not found.
CONNECTION_CAPABILITY_NOT_SUPPORTED
The provider does not support one of the requested capabilities.
CONNECTION_PROVIDER_NOT_SUPPORTED
This provider cannot be connected.
CONNECTION_REPLY_TO_REQUIRED
Set the email of the company before connecting the reply capture by email.