I am trying to test using the WLM APIs, and am encountering some interesting issues, wondering if anyone else has encountered similar. I can authenticate and get a token just fine. I can also run endpoints like v3/wlm/queues/{id}/consumers just fine.

My end goal is to add a new work item to the queue. I can capture information about an existing work item through v3/wlm/queues/{id}/workitems/{workItemID}, but attempting to add a new work item with v3/wlm/queues/{id}/workitems simply returns a 404 resource not found. Same queue, so can’t see it being permissions.

The queue is just for testing, so has a single column: PayerID. So the json returned from querying one of the existing work items looks like this:

{

    "json": {
        "PayerID": "12345679"
    }
}

When trying to add a new work item, not sure why it is not finding the resource. Note, I am adding it in as shown below because the docs show it is expecting an int64, but just for kicks I tried entering 8675309 as a string as well - no joy.

{
  "workItems": s
    {
      "json": {
        "PayerID": 8675309
      }
    }
  ]
}