You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Run script and receive error.
Invoke-RestMethod:
{
"errorName": "NotSupportedException",
"errorMessage": "RESTEASY003065: Cannot consume content type",
"trackingId": "ed660789826747a2a97eb71e32948ca6"
}
Expected behavior the work item to have been completed. Actual behavior NotSupportedException
Operating System (please complete the following information):
OS: [e.g. Windows 11 ]
CLI Environment [ Powershell ]
Additional context
Simple answer. The API Documentation page does not mention there needs to be a BODY in the POST. the body appears to be the entire workitem JSON object.
this also effects the SDK's
The text was updated successfully, but these errors were encountered:
Describe the bug A clear and concise description of what the bug is.
To Reproduce Steps to reproduce the behavior:
$headers = New-Object "System.Collections.Generic.Dictionary[[String],[String]]"
$headers.Add("Accept", "application/json")
$headers.Add("Authorization", "Bearer ")
$response = Invoke-RestMethod 'https://{tenant}.api.identitynow.com/v3/work-items/:id' -Method 'POST' -Headers $headers
$response | ConvertTo-Json
Invoke-RestMethod:
{
"errorName": "NotSupportedException",
"errorMessage": "RESTEASY003065: Cannot consume content type",
"trackingId": "ed660789826747a2a97eb71e32948ca6"
}
Expected behavior the work item to have been completed.
Actual behavior NotSupportedException
Operating System (please complete the following information):
Additional context
Simple answer. The API Documentation page does not mention there needs to be a BODY in the POST. the body appears to be the entire workitem JSON object.
this also effects the SDK's
The text was updated successfully, but these errors were encountered: