Fix API Authentication in n8n Workflow (HMAC-SHA1 Signature)

Fix API Authentication in n8n Workflow (HMAC-SHA1 Signature)

Fix API Authentication in n8n Workflow (HMAC-SHA1 Signature)

Upwork

Upwork

Remoto

9 hours ago

No application

About

If you want some quick cash and a great review, please read this job posting. I have an existing automation workflow built in n8n that needs to connect to the Farnell (element14) Product Search API to pull customer-specific contract pricing. I have all the necessary credentials (API Key, Customer ID, Secret Key), but I am consistently getting an "Invalid Password" or authentication error. The Farnell API uses a complex HMAC-SHA1 signature that includes a timestamp, which I have been unable to implement correctly. Here is the documentation on how to set it up: https://partner.element14.com/docs/read/Product_Search_API_REST__Description#signatures The final deliverable is a functional n8n HTTP Request node (and any necessary preceding Code nodes) that successfully retrieves contract pricing from the Farnell API without authentication errors. What I Will Provide: To help you get this done quickly, I will provide: All necessary credentials (API Key, Customer ID, Secret Key). The exported JSON of my current n8n workflow. A successful example URL provided by Farnell support. If you believe this is something you can do easily pleae let me know 🙂