CONNECTION_CAPABILITY_NOT_SUPPORTED

When it happens

The provider does not support one of the capabilities of the request; error.details.capability names it.

How to fix it

Send only the capabilities of the provider, or omit capabilities to get its default. See the provider catalog in the Connections guide.

Retry

Not as is: the same request fails the same way. Fix the cause described above, then send the request again, under a new Idempotency-Key if the body changed.

Returned by

The operations where this code is most likely. The list is not exhaustive.

• POST /v1/companies/{company_id}/connections

Example response

When this error occurs, the API answers 422 Unprocessable Content with a JSON body of this shape:

{
  "type": "https://docs.beel.es/errors/CONNECTION_CAPABILITY_NOT_SUPPORTED",
  "title": "CONNECTION_CAPABILITY_NOT_SUPPORTED",
  "detail": "The provider does not support one of the requested capabilities.",
  "instance": "/v1/<resource>",
  "errors": [],
  "success": false,
  "error": {
    "code": "CONNECTION_CAPABILITY_NOT_SUPPORTED",
    "message": "The provider does not support one of the requested capabilities.",
    "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

Keep exploring