I’m trying to send an HTTP request from my workflow in n8n using an OAuth1 API, but I’m running into an issue. n8n is asking me to provide the following parameters:
Authorization URL
Access Token URL
Request Token URL
The problem is that I don’t have these values. I’ve already configured the same request in Postman, and it works correctly there without needing to explicitly set these URLs.
Could you please help me understand why n8n requires these OAuth1 endpoints and how I can work around this if my API setup in Postman works without them?
If your API allows you to pass the OAuth signature in the header (which is what Postman does by default), you can bypass the “OAuth1” credential type entirely.
In Postman, send a successful request.
Go to the Headers tab in the response/request and find the Authorization header. It will look like OAuth oauth_consumer_key="..." , ....
In n8n, change the Authentication to Header Auth.
Create a new credential and set:
Name:Authorization
Value: Paste the entire string from Postman starting with OAuth...
Note: This only works if the tokens don’t expire quickly. If the oauth_nonce or oauth_timestamp are strictly validated for every single request, this method will fail after a few minutes.
For more n8n contents, check it out here: The Owl Logic
If it works on Postman, copy the CURL from Postman and import the CURL on n8n HTTP node. It will directly work.
However, if your tokens have an expiry, this will stop working on both Postman and on n8n.
To fix this - you need to configure a true OAuth Configuration that requires - Authorization URL, Access Token URL, Request Token URL. You will find these on your API Providers documentation, or you can ask AI Tools like ChatGPT, Claude or Gemini to get you these if the app is a popular one.