Hi, I have upgraded Airbyte to 0.50.4 on a test m...
# help-connector-development
x
Hi, I have upgraded Airbyte to 0.50.4 on a test machine and am trying to create a connector for the [Userflow](https://userflow.com/docs/api#userflow-api-reference) api. I've set up the connector as stated in the tutorial, create a stream for the endpoint
/users
and made sure (as stated in their doc) to prefix the API key (upon entering my Test Values) with
Bearer
. I'm facing the following error
Copy code
Could not verify streams:

"Invalid connector manifest with error: Validation against json schema defined in declarative_component_schema.yaml schema failed"

In order to test a stream, ensure that the YAML is structured as described in the docs.
Looking at the automatically imported schema it is pretty straightforward:
Copy code
{
  "$schema": "<http://json-schema.org/draft-07/schema#>",
  "additionalProperties": true,
  "properties": {},
  "type": "object"
}
Would you have any insight as to what I did wrong ? Thanks~
k
A message from kapa.ai
Hmm, I don't know enough to give you a confident answer yet. However, I can provide you with some resources that might help you with your issue. For understanding the YAML file and its structure, you can refer to the [YAML Reference](https://docs.airbyte.com/connector-development/config-based/understanding-the-yaml-file/reference) in the Airbyte documentation. Additionally, you can check out this [tutorial](https://airbyte.com/tutorials/extract-data-from-the-webflow-api) on building a connector to extract data from the Webflow API, which might give you some insights into creating a connector for the Userflow API. If you still face issues, consider asking for help on the [Airbyte forum](https://discuss.airbyte.io) or [Airbyte Slack](https://airbytehq.slack.com) for further assistance.
j
Looks like there is some problem in the manifest. Could you share it here?
x
Thanks a lot for your reply @Joe Reuter Here's the manifest I got from the connector builder UI.
I've tried changing the API authentication to
Bearer
instead of API key to see if it fixed it, to no avail
j
Are you seeing the "Invalid connector manifest with error: Validation against json schema defined in declarative_component_schema.yaml schema failed" error in the builder?
If yes, please try upgrading your stack, I just loaded your manifest into the builder on a cloud account (which is up to date) and it worked just fine
x
Thanks! Yes I've updated this morning to
0.50.5
(latest version on the github repo) and I still see the same error after loading the YML in the builder
j
Could you open the dev tools in chrome and check the "list" request (it should have status code 400)? Please copy paste the full response body here
x
sure
Copy code
{
  "detail": "Method Not Allowed"
}
j
That can't be the right one, it has to include the "Invalid connector manifest with error: Validation against json schema defined in declarative_component_schema.yaml schema failed" error message somehow
I seems like your setup somehow got into a weird state
x
yeah I'll do a clean install locally and re-check, thanks! Can't really afford that on production though so I'll have to investigate more thoroughly