I'm talking with the Fivetran support (Enterprise plan), and I'm telling some of them is sometimes violating the OpenAPI schema.

Also I'm sending like as following.

https://support.fivetran.com/hc/en-us/community/posts/13486977431575-Other-API-Needs-Fix-OpenAPI-schema-definition-s-all-response-object-properties-are-OPTIONAL

Here is the rough details of support interactions. I told connector list API endopoint (/v2/groups/{groupId}/connectors) output is violating the OpenAPI Schema.

It's returning null on some fields like connected_by, setup_tests, private_link_id, proxy_agent_id. But they're not allowed to be null.

OpenAPI is asserting like following:

private_link_id:
  type: string 

I know, it's common to confuse optionals and nulls, so I noted the reference.

https://json-schema.org/understanding-json-schema/reference/null

But the support keeps shifting the point. They're ...

- advice to touch Web UI to change the state, to change it to non-null values.

  - Even so, API must follow the schema. To know the current state is one of the purpose of API.

- advice to make null acceptable to make the app robust.

  - I also can't believe they're using the word "robust" in such way.

  - And if thinking so, should we also consider any kind of API violations? To consider possibly null, string, number, array, etc.. for all fields? To limit such consideration, we have the schema as contraction.

- suggest have the video call without responding my messages, as they thought it's not good to make long email chain.