CONNECTION_PROVIDER_NOT

This provider cannot be connected.


HTTP status	`422` Unprocessable Content
Retry	After fixing the cause

When it happens

BeeL. does not connect that provider.

How to fix it

Use a provider from the 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_PROVIDER_NOT_SUPPORTED",
  "title": "CONNECTION_PROVIDER_NOT_SUPPORTED",
  "detail": "This provider cannot be connected.",
  "instance": "/v1/<resource>",
  "errors": [],
  "success": false,
  "error": {
    "code": "CONNECTION_PROVIDER_NOT_SUPPORTED",
    "message": "This provider cannot be connected.",
    "details": {}
  },
  "meta": {
    "timestamp": "2026-05-21T10:00:00Z",
    "request_id": "4bf92f3577b34da6a3ce929d0e0e4736"
  }
}