Hi, around the 10:40 mark, you show how to add the body params and the authorization - but from the time you get the "invalid grant", pause the recording for a minute, and come back - there is information in the "Params" section of the post - but never go over it. I am getting a server error when I try this on my end, and feel what you have in your params portion might help with this. Can you please share?
Hello, if you are getting an invalid_grant error at this point, we recommend redoing the previous GET step and immediately copying the authorization code to the POST request. It expires rather quickly, which is likely why you are getting an error after pausing.
@@EideBailly Sorry, I am getting a 500 server error and a 401 Authorization error. The "invalid grant" was in reference to where you were at in the video where I got stuck with these other errors.
@@stagarmsofficial If you look at the URL displayed at 10:50, you can see that there have been no parameters added to the request that was actually made (there were no edits to the URL). While changes were made during troubleshooting, they were ultimately not related to the solution, which is why they were flagged in Postman as existing but not discussed. While recording, our consultant’s fix was to go back and get a new code and ensure that there was no leading or trailing whitespace or non-printing characters in what he pasted from his browser URL bar. However, the error he received was a 400 Bad Request, so it may not resolve your 500 and 401 errors. You may wish to consult the help center at docs.oracle.com/en/cloud/saas/netsuite/ns-online-help/index.html for more information on how to resolve. If the help center does not address your concerns or if you have additional questions, you can reach out for more hands-on support with our team here: www.eidebailly.com/technology-support. Thank you!
Thanks for reaching out! In our experience, when the Netsuite side is set up properly and everything seems correct in the API call but the invalid_grant error happens there are three most likely scenarios. The first is the one seen in the video, where there is some extra whitespace, likely at the end of the code value, from copy / pasting it in. The second is that the authorization code may have expired as it is very short-lived. And the third is there is a mistake somewhere in the netsuite setup or a typo overlooked in the API call. A common one we see is making sure the key is redirect_uri (note the lowercase i) vs redirect_url (lowercase L).
Hi, I don't know if this will help anyone else getting a 500 Internal Service error, but during the Postman part make sure you're typing "redirect_uri" and NOT "redirect_url" (the difference being, if you can't see it, the last letter is a lowercase "i" and NOT a lowercase "L". I know most people are familiar with redirect_uri, but sometimes you can get lost in just following along that it doesn't stand out.
Fantastic. I spent a couple of hours today (before I saw the video) banging my head again a wall today trying to follow the docs and get this setup.
Oh no! We hope the video was helpful and solved the issue for you. Thanks for watching!
Thank you so much for this video!!
Thank you for watching! 😃
Hello, Thank you very much but How can I get value of "code_verifier" at 10:50 mark. Because this field is required?
so every 3,600 seconds I need to refresh my access token right?
Hi, around the 10:40 mark, you show how to add the body params and the authorization - but from the time you get the "invalid grant", pause the recording for a minute, and come back - there is information in the "Params" section of the post - but never go over it. I am getting a server error when I try this on my end, and feel what you have in your params portion might help with this. Can you please share?
Hello, if you are getting an invalid_grant error at this point, we recommend redoing the previous GET step and immediately copying the authorization code to the POST request. It expires rather quickly, which is likely why you are getting an error after pausing.
@@EideBailly Sorry, I am getting a 500 server error and a 401 Authorization error. The "invalid grant" was in reference to where you were at in the video where I got stuck with these other errors.
@@stagarmsofficial If you look at the URL displayed at 10:50, you can see that there have been no parameters added to the request that was actually made (there were no edits to the URL). While changes were made during troubleshooting, they were ultimately not related to the solution, which is why they were flagged in Postman as existing but not discussed.
While recording, our consultant’s fix was to go back and get a new code and ensure that there was no leading or trailing whitespace or non-printing characters in what he pasted from his browser URL bar. However, the error he received was a 400 Bad Request, so it may not resolve your 500 and 401 errors.
You may wish to consult the help center at docs.oracle.com/en/cloud/saas/netsuite/ns-online-help/index.html for more information on how to resolve.
If the help center does not address your concerns or if you have additional questions, you can reach out for more hands-on support with our team here: www.eidebailly.com/technology-support.
Thank you!
@@EideBailly it worked, thank you
@@MekanJuma we're happy to hear that. Thanks for tuning in!
my post getting the same "invalid_grant", but all fields seems valid any idea why?
Thanks for reaching out! In our experience, when the Netsuite side is set up properly and everything seems correct in the API call but the invalid_grant error happens there are three most likely scenarios. The first is the one seen in the video, where there is some extra whitespace, likely at the end of the code value, from copy / pasting it in. The second is that the authorization code may have expired as it is very short-lived. And the third is there is a mistake somewhere in the netsuite setup or a typo overlooked in the API call. A common one we see is making sure the key is redirect_uri (note the lowercase i) vs redirect_url (lowercase L).
Hi, I am getting 500 Internal Server Error at token generation
Hi, I don't know if this will help anyone else getting a 500 Internal Service error, but during the Postman part make sure you're typing "redirect_uri" and NOT "redirect_url" (the difference being, if you can't see it, the last letter is a lowercase "i" and NOT a lowercase "L". I know most people are familiar with redirect_uri, but sometimes you can get lost in just following along that it doesn't stand out.
@@lukerulemerrillmfg Thank you for pointing this out.