Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Bug] Your Bug Report Here Requesting changes to 'Complete a Work Item' (complete-work-item) #645

Open
kevin-gorton-sp opened this issue Oct 14, 2024 · 0 comments

Comments

@kevin-gorton-sp
Copy link

Describe the bug A clear and concise description of what the bug is.

To Reproduce Steps to reproduce the behavior:

  1. Go to 'API Documentation'
  2. Click on 'Powershell (or other method)'
    $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
  3. Copy script into PowerShell
  4. 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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

No branches or pull requests

1 participant