Topic Started
This user has not created any forum posts.
Replies Created
Reply to: 400 Bad Request error using POSTMAN
Friday, June 23, 2023 at 03:54pmSubscriptions
Topics | Replies | Freshness | Views | Users |
---|---|---|---|---|
Canada SBX = sandbox.e-signlive.ca API = /apitoken/clientApp/accessToken https://sandbox.e-signlive.ca/apitoken/clientApp/accessToken |
8 | 10 months ago | 21,606 |
Subscriptions Release Notes
This user is not subscribed to any release notes.
I had this same issue. For anyone still running into this, the problem for me was the type parameter being set to "Owner" instead of "OWNER".
Here is an example cURL request that should work if you use an appropriate client ID and secret.
curl -d '{"clientId":"yourClientId","secret":"yourSecret","type":"OWNER"}' -H "Content-Type: application/json" https://sandbox.esignlive.com/apitoken/clientApp/accessToken -i
The original post shows "OWNER" so I'm not sure if it would resolve their issue. A potential resolution for the issue if you are using "OWNER" and still getting this error could be that you're using the wrong sandbox URL. For example, "https://sandbox.esignlive.com" vs "https://sandbox.e-signlive.com". The correct one is the one that displays when you sign into the sandbox account in the browser.