![]() ![]() To check, let’s first navigate to the Method Execution of your endpoint as shown.įrom there, you’ll see the field Authorization. I am not referring to the API Keys you can add to your endpoint, those return a separate error when not attached correctly. There is one more thing to check - the authorization settings. If you’ve made it this far, you’ve verified that your URL path is correct and that the latest version of your API is deployed. If it does, you’re golden! If not, continue to the next section to check one last thing. To test this out, you can curl the URL or toss it in your browser location window to see if it works. Once that comes up, you’ll see the full URL path highlighted in blue as shown below. Navigate to the Stages section of your API, and then click on the HTTP method for the endpoint you want. A common mistake that users make is that they copy a portion of the Gateway url but miss the ending for that specific endpoint. This might seem elementary, but first double check that you are using the entire URL for the endpoint that you want. If you are unsure of how to get the URL for your endpoint, keep reading below to see how to find it. Leave a note if you’d like, but otherwise you’re all set with the deploy!ĭon’t forget, for every change that you make, you need to redeploy your API to make sure that those changes get published to the Internet. If you already have set up stages, deploy to the one of your choosing, but if not, create one with whatever name you’d like. Click on Deploy API, where it will bring you to a configuration modal. Navigate to your API and click on the Actions tab as seen in the screenshot above. Without doing this, you’ll never be able to see your API in the real world. Using the Gateway’s built-in deploy functionality allows for you to publish new changes to the Internet. ![]() While you have tested your endpoint in the console and seen the results you wanted, you need to deploy your changes as well. When this happens, there are three areas to check that will save you some debugging headaches. The JSON returned from your endpoint might look like the following: The test method inside Method Execution might run fine, but you can’t access your new endpoint on the internet. As you’ve been working on setting up new endpoints via API Gateway, dealing with authentication errors can be pretty frustrating. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |