I agree, I tried implementing this myself but ended up having to do them in HTTP Request - Core.

The reason was that the required headers in the authorization request require Jinja with filters in the additional headers in the custom integration section. But when the test request is done the additional headers do not render, they stay as the Jinja source.

For context here is the required headers from API Docs from DNSME, below is the API key in their documentation for the API, not my own.

x-dnsme-apiKey:1c1a3c91-4770-4ce7-96f4-54c0eb0e457a

x-dnsme-requestDate:Sat, 12 Feb 2011 20:59:04 GMT

x-dnsme-hmac:b3502e6116a324f3cf4a8ed693d78bcee8d8fe3c

x-dnsme-apiKey The API Key for your account. Refer to

the Config – Account Information menu once logged in to find this value.

x-dnsme-requestDate Standard HTTP-formatted date. This date is used to protect against falsified requests played back at a future time.

x-dnsme-hmac HMAC hash of value of the x-dnsmerequestDate

field. Refer to the DNS Made Easy REST API Documentation v2.0 Authentication section for more details on how to generate this value.

Piping the dnsmerequest data to jinja filter hmac with sha1 algo and the key being the dnsmerequestdate string does not work because it is not rendering