How Do I Fix the HTTP Token Error When Authenticating the DataForSEO API in n8n?

It looks like the error is coming from using your email address (which contains a “@” symbol) as the header name. In n8n’s header authentication configuration the “Name” field must be a valid HTTP token (only letters, digits, hyphens, etc.) and cannot contain special characters like “@”.

Below are some steps to address this issue:

1. Double-check the DFSEO API documentation
   Verify what header names the API requires. It’s very likely that the API expects a header with a valid name (for example, something like “Authorization” or a custom header such as “X-DataforSEO-Client”) and your email might be meant as the header value or part of a combined value.

2. Update your n8n header credentials
   In your HTTP Request (or dedicated credentials) node:

   • Replace the header “Name” field that incorrectly contains your email with the proper header key as dictated by the API docs.
   • Use your email (and API key if needed) as part of the header “Value” rather than as the header “Name”. For example, if the API requires an Authorization: APIKEY <your-key> header or something that includes your email, then build the header value accordingly.

3. Re-test the node
   Once you’ve updated and saved the correct header configuration, run the node again to verify that the error no longer occurs.

If you’re unsure of the required header format for DataForSEO, check the DataForSEO API documentation or contact their support. The key takeaway is that header names need to be valid HTTP tokens and should not include characters like “@”.

The error message indicates that an invalid header name is being used—specifically, your email is getting set as a header name (i.e. as “[steve@myemail.com]”), which is not allowed. HTTP header names must be valid tokens without extra characters (like square brackets).

Here are some steps to resolve the issue:

1. Check How You’re Supplying Credentials:
   Ensure that you’re not accidentally entering your email in a field where it becomes a header name. If DataforSEO uses Basic Auth, the email (username) and API key (password) should be combined into an Authorization header. For example, you can set the Authorization header as follows:

   Authorization: Basic <base64encoded(email:apiKey)>
   

   In n8n, it’s best to use the built-in authentication options rather than manually adding credentials as custom headers.

2. Review the HTTP Request Node Settings:
   Double-check the node configuration. Make sure that any header fields you add manually have valid header names (typically they use names like “Authorization”). Remove any square brackets or markdown formatting from the header key.

3. Follow the Service’s Documentation:
   The DataforSEO API likely expects specific instructions on how to authenticate. Verify from their documentation that you are using the correct method (e.g., HTTP Basic Auth) and that you’re not placing your email in a header key.

By correcting your node’s configuration to ensure credentials are provided in the proper fields (and not as custom header keys), you should resolve the “Header name must be a valid HTTP token” error.

Based on the error message, it looks like the email is being treated as a header name rather than as a value. In HTTP, header names must be valid tokens (letters, digits, hyphens, etc.) and cannot contain special characters like @. This usually happens when the email has been placed or parsed into the header name field.

Here are some steps to check and resolve the issue:

1. Review the Credentials Setup:
   Make sure you’re setting the email and API key in the proper authentication fields. If DataforSEO expects basic authentication, configure the HTTP Request node to use Basic Auth so that n8n automatically puts the email as the username and API key as the password.

   Example Basic Auth configuration:

   JSONCopied
   {
     "authentication": "basicAuth",
     "username": "steve@myemail.com",
     "password": "YOUR_API_KEY"
   }

2. Check Custom Headers:
   Look at the Headers section in the HTTP Request node. Ensure you haven’t manually added a header where the header name is your email (e.g., [steve@myemail.com]). If you see your email in the header name field, remove it or correct it so that it’s passed as a value instead.

3. Verify API Requirements:
   Some APIs require credentials to be sent in the request body or as URL parameters, not in headers. Double-check the DataforSEO API documentation to ensure you’re using the proper method.

4. Avoid Unnecessary Formatting:
   If you’ve copied a sample or used markdown formatting (like wrapping the email in square brackets or mailto links), remove that formatting. The HTTP Request node expects plain text.

By ensuring that the email and API key are used in the authentication settings and that no header name is set to your email, you should be able to resolve the “Header name must be a valid HTTP token” error.

Let me know if you need any further details on configuring the node.