You have to make sure that your signature base string parameters are in alphabetic order by parameter name
This is what i'm using to encode parameters in my signature base.
var result = new StringBuilder();
string webUnreservedChars = "abcdefghijklmnopqrstuvwxyzABCDEFGHIJKLMNOPQRSTUVWXYZ0123456789-_.~";
foreach (char symbol in url)
{
if (webUnreservedChars.IndexOf(symbol) != -1)
result.Append(symbol);
else
result.Append('%' + ((int)symbol).ToString("X2"));
}
return result.ToString();
If all credentials and URLs are correct and existing, the issue might happen because of time synchronization issues of your local with remote (it is important for signatures validation).
Best Answer
If you supply all of those values, you don't have to use the access or request routes. postman will take care of the rest.
Typically I've noticed that some routes are slightly different; ie.
use: http://your url here/rest/V1/products?searchCriteria=
instead of: http://your url here/rest/V1/products?searchCriteria
Notice the difference with the =
The only time you need to use those routes are when you post to your callback and identity urls.