It would be helpful to support the Authorization HTTP header when adding a reconciliation service. In this way, a private reconciliation service can be supported.

Currently, Authorization and other headers are supported when adding a column by fetching URLs, but not supported when adding a reconciliation service.

Proposed solution

Support HTTP header customization when adding reconciliation services.

Alternatives considered

Workarounds I considered include to deploy the private reconciliation service in a private network or to use URL parameters for authentication.

Additional context

Adding a screenshot of the current HTTP header customization function in the "Add Column by Fetching URL" function.