Hey all, we have a custom MS Entra ID connector that we forked and seems to not accept creating a new source via the API (I'm using Postman for the request in this case). The reason seems to be that it does not accept

microsoft-entra-id

as the

sourceType

, I got that value from the source code of the connector. The request body is as follows:

{
  "name": "microsoft_entra_id_test",
  "workspaceId": "{{WORKSPACE_ID}}",
  "configuration": {
    "sourceType": "microsoft-entra-id",
    "start_date": "2017-01-25T00:00:00Z",
    "enable_experimental_streams": false,
    "credentials": {
      "credentials_title": "OAuth Credentials",
      "client_id": "{{CLIENT_ID}}",
      "client_secret": "{{CLIENT_SECRET}}",
      "refresh_token": "{{REFRESH_TOKEN}}"
    }
  }
}

Response:

{
  "status": 400,
  "type": "[<https://reference.airbyte.com/reference/errors](https://reference.airbyte.com/reference/errors)>",
  "title": "value-not-found",
  "detail": "The submitted value could not be found.",
  "documentationUrl": null,
  "data": {
    "value": "microsoft-entra-id"
  }
}

This throws an error, saying it cannot find the

sourceType

of that value. This can be right since the connector we are using is a custom one so I requested the source details to see what kind of

sourceType

it needs to work, it said it was set as an empty string:

{
  "sourceId": "8cf5d308-7056-45e5-8948-11d217607019",
  "name": "Microsoft Entra Id",
  "sourceType": "",
  "definitionId": "9e1d5c73-b7a2-4642-b224-f78379fdf4d5",
  "workspaceId": "7d4c5653-bd89-454a-b520-173e77c68fc8",
  "configuration": {
    "user_id": "**********",
    "client_id": "**********",
    "tenant_id": "**********",
    "client_secret": "**********",
    "__injected_declarative_manifest": {},
    "__injected_components_py_checksums": {}
  },
  "createdAt": 1761225116
}

That's fine, however, setting it to an empty string yields the same response:

{
  "name": "microsoft_entra_id_test",
  "workspaceId": "{{WORKSPACE_ID}}",
  "configuration": {
    "sourceType": "",
    "start_date": "2017-01-25T00:00:00Z",
    "enable_experimental_streams": false,
    "credentials": {
      "credentials_title": "OAuth Credentials",
      "client_id": "{{CLIENT_ID}}",
      "client_secret": "{{CLIENT_SECRET}}",
      "refresh_token": "{{REFRESH_TOKEN}}"
    }
  }
}

Response:

{
  "status": 400,
  "type": "[<https://reference.airbyte.com/reference/errors](https://reference.airbyte.com/reference/errors)>",
  "title": "value-not-found",
  "detail": "The submitted value could not be found.",
  "documentationUrl": null,
  "data": {
    "value": ""
  }
}

Is there any idea what I need to add to

sourceType

? I thought it was

microsoft-entra-id

but that does not work. Many thanks!

Based on the information in the knowledge sources, the error you are encountering (

value-not-found

for

sourceType: "microsoft-entra-id"

) is a common issue when using the Airbyte Public API to create sources for connectors that are not mapped in the backend's name-to-definition mapping. This mapping is what allows the API to resolve a

sourceType

string (like

"microsoft-entra-id"

) to the correct connector definition. If your connector is custom or not included in this mapping, the API will not recognize the

sourceType

and will return the error you are seeing. This issue has been reported for other connectors as well, such as

google-drive

and

brevo

, where the connector is available in the UI but not recognized by the API because the mapping is missing or out of sync with the available connectors. In those cases, the workaround is to use the

definitionId

instead of

sourceType

in your API request. The

definitionId

is the UUID of the connector definition, which you can retrieve from the Airbyte UI or via the API if you list available connector definitions. When you use

definitionId

, the API does not need to resolve the string name and can directly use the connector you specify. Here is how you should structure your request:

json {   "name": "microsoft_entra_id_test",   "workspaceId": "{{WORKSPACE_ID}}",   "definitionId": "{{DEFINITION_ID}}",   "configuration": {     "start_date": "2017-01-25T00:00:00Z",     "enable_experimental_streams": false,     "credentials": {       "credentials_title": "OAuth Credentials",       "client_id": "{{CLIENT_ID}}",       "client_secret": "{{CLIENT_SECRET}}",       "refresh_token": "{{REFRESH_TOKEN}}"     }   } }

Replace

{{DEFINITION_ID}}

with the actual definition ID of your custom Microsoft Entra ID connector (which you can find in the source details you posted:

"definitionId": "9e1d5c73-b7a2-4642-b224-f78379fdf4d5"

). Key points: - The

sourceType

field is only recognized if the connector is mapped in the backend. For custom connectors, this is often not the case. - Use the

definitionId

field instead of

sourceType

to create a source for a custom connector via the API. - This approach is supported by the Airbyte Public API documentation, which states: "One of configuration.sourceType or definitionId must be provided" and provides an example using

definitionId

 [Airbyte Public API - createSource](https://reference.airbyte.com/reference/start). If you use

definitionId

, your request should succeed as long as the rest of your configuration is correct. If you continue to have issues, ensure your custom connector is properly registered and available in your Airbyte instance, and that you are using the correct

definitionId

for your connector. --- References: - [Airbyte Public API - createSource](https://reference.airbyte.com/reference/start) - [Issue with value-not-found for unmapped connectors](https://github.com/airbytehq/airbyte/issues/49731) - [Similar issue for google-drive connector](https://github.com/airbytehq/airbyte/issues/35653)

Thanks @kapa.ai, posting the

definitionId

is not accepted:

{
  "name": "microsoft_entra_id_test",
  "workspaceId": "{{WORKSPACE_ID}}",
  "configuration": {
    "definitionId": "9e1d5c73-b7a2-4642-b224-f78379fdf4d5",
    "start_date": "2017-01-25T00:00:00Z",
    "enable_experimental_streams": false,
    "credentials": {
      "credentials_title": "OAuth Credentials",
      "client_id": "{{CLIENT_ID}}",
      "client_secret": "{{CLIENT_SECRET}}",
      "refresh_token": "{{REFRESH_TOKEN}}"
    }
  }
}

Response:

{
  "status": 422,
  "type": "<https://reference.airbyte.com/reference/errors#unprocessable-entity>",
  "title": "unprocessable-entity",
  "detail": "The body of the request was not understood",
  "documentationUrl": null,
  "data": null
}

A message from kapa.ai

@kapa.ai, I see but now there's another error:

{
  "name": "microsoft_entra_id_test",
  "workspaceId": "{{WORKSPACE_ID}}",
  "definitionId": "9e1d5c73-b7a2-4642-b224-f78379fdf4d5",
  "configuration": {
    "start_date": "2017-01-25T00:00:00Z",
    "enable_experimental_streams": false,
    "credentials": {
      "credentials_title": "OAuth Credentials",
      "client_id": "{{CLIENT_ID}}",
      "client_secret": "{{CLIENT_SECRET}}",
      "refresh_token": "{{REFRESH_TOKEN}}"
    }
  }
}

This is the response:

{
  "status": 500,
  "type": "<https://reference.airbyte.com/reference/errors>",
  "title": "unexpected-problem",
  "detail": "An unexpected problem has occurred. If this is an error that needs to be addressed, please submit a pull request or github issue.",
  "documentationUrl": null,
  "data": {
    "message": "io.airbyte.data.exceptions.ConfigNotFoundException: config type: STANDARD_WORKSPACE id: 496177ae-6b44-4e41-82b2-8d88be82e55d"
  }
}

A message from kapa.ai

@kapa.ai Thanks I think that is helping, after correcting the workspace I got the following error:

{
  "name": "microsoft_entra_id_test",
  "workspaceId": "{{WORKSPACE_ID}}",
  "definitionId": "9e1d5c73-b7a2-4642-b224-f78379fdf4d5",
  "configuration": {
    "start_date": "2017-01-25T00:00:00Z",
    "enable_experimental_streams": false,
    "credentials": {
      "credentials_title": "OAuth Credentials",
      "client_id": "{{CLIENT_ID}}",
      "client_secret": "{{CLIENT_SECRET}}",
      "tenant_id": "1234",
      "user_id": "1234",
      "refresh_token": "{{REFRESH_TOKEN}}"
    }
  }
}

Response:

{
  "status": 422,
  "type": "<https://reference.airbyte.com/reference/errors#unprocessable-entity>",
  "title": "unprocessable-entity",
  "detail": "The body of the request was not understood",
  "documentationUrl": null,
  "data": {
    "message": "json schema validation failed when comparing the data to the json schema. \nErrors: $: required property 'client_id' not found, $: required property 'client_secret' not found, $: required property 'tenant_id' not found, $: required property 'user_id' not found "
  }
}

A message from kapa.ai

This has fixed it. 👍

A message from kapa.ai