.png){kind=logo}
Troubleshooting Clay HTTP API Basic Authentication for WordPress Integration
Hello Clay Support Team, I am currently experiencing an issue with the HTTP API function when trying to authenticate a request using Basic Authentication. My goal is to integrate Clay with my WordPress site via the REST API, specifically to create a draft post. Problem Details: When configuring the Authorization header in the HTTP API function, I am using the following format:
css
H
Authorization: Basic <base64-encoded(username:application_password)>However, despite entering the header in this format, I am receiving the following error:
Invalid character in header content ["Authorization"]
I have verified that:
- 1.
There are no extra spaces or line breaks in my Authorization header.
- 2.
The base64 encoding is correct and works in external tools like Postman.
- 3.
The header is formatted as a single continuous line, but Clay’s UI appears to add line breaks automatically.
This error persists even after confirming that the credentials, endpoint, and other settings are accurate. Request: Could you please assist with the following?
- 1.
Confirm whether Clay’s HTTP API function supports long Authorization headers (particularly for Basic Authentication).
- 2.
Provide any possible workarounds if line breaks in long headers are known to cause issues.
Thank you for your help. I’m looking forward to your guidance on resolving this issue so that I can successfully complete this integration.
