- Newest
- Most votes
- Most comments
Hi, if you are calling the API by directly POST to the API uri, then you might need to fill in the ${workspaceId}
in the uri path.
Depending on your development environment, we do recommend you use AWS CLI (if you are testing in terminal) or AWS SDK (you can find all coding language there), where you don't need to manually construct API uri. TwinMaker is generally available so all TwinMaker APIs are included in the most recent AWS CLI/SDK version.
Using AWS CLI: https://docs.aws.amazon.com/cli/latest/userguide/cli-chap-using.html
Using AWS SDK: https://aws.amazon.com/developer/tools/
Let us know if you still have any issues.
Based on the information shared by you, I believe that you are using http client like postman/curl to call the API. If yes, then please note that there is a problem either with the authorization header you are providing or the endpoint you are using.
The endpoint that you should be using with http clients is "data.iottwinmaker.us-east-1.amazonaws.com " instead of instead of "iottwinmaker.us-east-1.amazonaws.com ".
You are correct, I'm calling it from the browser, the full request URL is
https://api.iottwinmaker.eu-west-1.amazonaws.com/workspaces/CookieFactory/entity-properties/value
. I have setup the authorization and I'm able to call other api from TwinMaker as well, for exampleListEntities
with filters, so I don't think the authorization header is the issue I'm facing
Relevant content
- asked a year ago
- asked 8 months ago
- asked 10 months ago
- asked 9 months ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated 7 months ago
Hi Hao, thanks for your answer but I've add the workspaceId in the request, the full request URL is
https://api.iottwinmaker.eu-west-1.amazonaws.com/workspaces/CookieFactory/entity-properties/value