Object Requests REST API

Published: 2026-08-31

Last Updated: 2026-09-01

List or delete object requests in MDCMS.

Authorization

A missing or invalid token returns HTTP 401 Unauthorized.

GET

Return object requests in MDCMS. Optional query parameters further limit the list by request number, application, level, RFP, reason, status, create status, object type, attribute, object name, source name, user, Git repository, branch, or linked project, task, and subtask.

GET /object-requests

Query parameters

All parameters are optional. Omit all parameters to return every object request.

project, task, and subtask can be combined. When any of them is supplied, only object requests with a matching project/task/subtask assignment are returned. Each matching request still includes every project/task/subtask assignment in the tasks array.

Example

Replace {endpoint} with the URL endpoint defined for the MDCMS HTTP server.

curl -H "Authorization: Bearer {token}" \
  "https://{endpoint}/object-requests?appl=TEST&lvl=10&reason=modify&objectName=MDWS&project=DEMO044"

GET /object-requests?appl=TEST&lvl=10&reason=modify&objectName=MDWS&project=DEMO044 HTTP/1.1
Host: {endpoint}
Authorization: Bearer {token}

Response body

Schema

Object request object

Task object

Example

{
  "objectRequests": [
    {
      "objectId": 45281,
      "appl": "TEST",
      "lvl": 10,
      "rfp": 1340,
      "reason": "modify",
      "status": "00",
      "createStatus": "created",
      "objectType": "*PGM",
      "attr": "SQLRPGLE",
      "objectName": "MDWSREQS",
      "sourceName": "MDWSREQS",
      "user": "MMORGAN",
      "repoId": "MDCMS",
      "branch": "V8.6-83",
      "fromObjectLibrary": "MMORGAN13",
      "fromSourceLibrary": "MMORGAN13",
      "fromSourceFile": "QRPGLESRC",
      "tasks": [
        {
          "project": "DEMO044",
          "task": 2,
          "subtask": 3
        }
      ]
    },
    {
      "objectId": 45290,
      "appl": "TEST",
      "lvl": 10,
      "rfp": 0,
      "reason": "recompile",
      "status": "00",
      "createStatus": "",
      "objectType": "*FILE",
      "attr": "PF",
      "objectName": "MDDCMSD",
      "sourceName": "MDDCMSD",
      "user": "MMORGAN",
      "repoId": "",
      "branch": "",
      "fromObjectLibrary": "MMORGAN13",
      "fromSourceLibrary": "MMORGAN13",
      "fromSourceFile": "QDDSSRC",
      "tasks": [
        {
          "project": "DEMO044",
          "task": 2,
          "subtask": 0
        },
        {
          "project": "DEMOCH",
          "task": 1,
          "subtask": 0
        }
      ]
    }
  ]
}

When no matching object requests are found, the API returns HTTP 221 with message No object requests found.

DELETE

Delete object requests that match the query parameters. Each matching request is returned with flags that show whether the request, source, and object were deleted.

A request is deleted only when its status is 00 or 01. If the request is assigned to an RFP, that RFP must be in status 00, 01, or SE.

The owner of the authentication token must be authorized in MDSEC for the request's application and level: code 38 to delete a request they own, or code 31 to delete a request owned by another user. Requests that fail these checks are left in place and reported in the response with requestDeleted set to false.

DELETE /object-requests

Query parameters

Each parameter is optional, but the request must include at least one of these combinations:

• objectId greater than 0
• rfp greater than 0
• appl, lvl greater than 0, and user
• project and task greater than 0

If none of those combinations is present, the API returns HTTP 400 Bad Request.

When more than one parameter is supplied, they are combined. For example, objectId with appl deletes the request only if it also belongs to that application.

Boolean parameters accept true, yes, y, or 1. Matching is case-insensitive. Any other value, including omitting the parameter, is treated as false.

project, task, and subtask can be combined. When any of them is supplied, only object requests with a matching project/task/subtask assignment are deleted.

Source and object in the developer library are not deleted for every request. For example, they are left in place for delete and update reasons, for *DTAGRP, *DUMMY, and *PIPE objects, and when the request was generated from another level. The sourceDeleted and objectDeleted flags in the response show what actually occurred.

Example

Delete the object requests assigned to an RFP, and delete matching source and objects from the developer libraries. Replace {endpoint} with the URL endpoint defined for the MDCMS HTTP server.

curl -X DELETE \
  -H "Authorization: Bearer {token}" \
  "https://{endpoint}/object-requests?rfp=1340&deleteSource=true&deleteObjects=true&closeEmptyRfps=true"

DELETE /object-requests?rfp=1340&deleteSource=true&deleteObjects=true&closeEmptyRfps=true HTTP/1.1
Host: {endpoint}
Authorization: Bearer {token}

Response body

The response is HTTP 200 even when some matching requests are not deleted. Inspect requestDeleted and errorMessage for each item. When no requests match the filters, objectRequests is an empty array.

Schema

Deleted object request object

Error messages

Example

{
  "objectRequests": [
    {
      "objectId": 45281,
      "objectName": "MDWSREQS",
      "attr": "SQLRPGLE",
      "requestDeleted": true,
      "sourceDeleted": true,
      "objectDeleted": true,
      "errorMessage": ""
    },
    {
      "objectId": 45290,
      "objectName": "MDDCMSD",
      "attr": "PF",
      "requestDeleted": false,
      "sourceDeleted": false,
      "objectDeleted": false,
      "errorMessage": "Object Request not in valid Status for Deletion"
    }
  ]
}

Related resources