If you’re sure the workspace exists, a 404 response could also mean an unauthorized API token. Be sure you’re using a valid User or Team API token with Write or Apply access to that workspace.
Thanks for the quick reply Chris.
I created the workspace using the API, so I don’t believe its the token.
Although, I’m using an organization token instead of a team token.
I was just reading the information on TC:
The organization API token is used to manage teams, team membership and workspaces. This token does not have permission to perform plans and applies in workspaces.
So probably this is my issue. I will test it and come back.
Came across this while getting the same issue, I wrapped the JSON in “data”{…} besides “type” : “runs” and that fixed it for me.
‘{
“type”: “runs”,
“data”:{“attributes”: {
“is-destroy”:true,
“message”: “Triggered Destroy”
},
“relationships”: {
“workspace”: {
“data”: {
“type”: “workspaces”,
“id”: “”
}
}
}
}}’