Convert a legacy Bedrock configuration into a managed credential Lets an organization that configured Bedrock before named credentials existed take ownership of that configuration so it can be edited or removed, without having to add a second credential first.

Error

A valid request URL is required to generate request examples

{
  "status": "ok",
  "results": "<unknown>"
}

{
  "error": {
    "name": "<string>",
    "statusCode": 123,
    "data": "<unknown>",
    "message": "<string>"
  },
  "status": "error"
}

POST

api

provider-credentials

adopt-legacy

Error

A valid request URL is required to generate request examples

{
  "status": "ok",
  "results": "<unknown>"
}

{
  "error": {
    "name": "<string>",
    "statusCode": 123,
    "data": "<unknown>",
    "message": "<string>"
  },
  "status": "error"
}

Converted the legacy Bedrock configuration

status

enum<string>

required

Available options:

ok

results

any