REST API Connector and OpenAPI spec

[amplication]

REST API Connector and OpenAPI spec

[iddan]

I'll need to dig deeper into this. Can you give a few examples?

[yuval-hazaz]

Example:
The header field or the URL field of a request may contain dynamic text like input.Key or other expressions. This expression may be saved as a string with no issue but we may use a special type for expressions which is not part of the OpenAPI document type.

Example:
An API may request a fixed header like "content" for all requests.
When a developer creates a connector to be published to the Library he can flag this header as "invisible" so the developer that is using the connector will not see this header as part of the configuration.

I assume that there could be more features or configurations like this that are proprietary to our solution and will be required as part of the connector configuration.

[iddan]

I don't understand the first example, can you give a concrete data example?

As far as I understand we can extend the OpenAPI format to include these features.