RestAPI - RecordsManagement - Delete RMClassification from existing document

I am using the RestAPI calls to Content Server and also the Recordsmanagement RestAPI interface.

https://developer.opentext.com/ce/products/content-management/apis/records-management-25-3-0

All RestAPI are working but I cannot delete an existing RMClassification from an existing document.

When calling the DELETE: /v1/nodes/11126409/rmclassifications/1934770 with the correct DocID and RMClassification I get a response:

#status#	HTTP/1.1 404 Not Found

I also provide the rm_metadataToken.

A GET api/v1/nodes/11126409/rmclassifications works correctly

and Also a PUT api/v1/nodes/11126409/rmclassifications works correctly

But removing a RM category from a document does not seem te be working.

Does anyone know where to look and if this RestAPI operation in Content Server is working correctly?

Thx.

Find more posts tagged with

Note:

If there are Accepted Answers, those will be shown by default. You can switch to 'All Replies' by selecting the tab below.

Accepted answers

All comments

Clarke

Hey,

I had a look at this in my 24.3 system.

var url = "[LL_REPTAG_URLPREFIXFULL /]/api/v1/nodes/[LL_REPTAG_&targetID /]/classifications/[LL_REPTAG_&classificationID /]";

Seems the REST command isn't there / isn't registered.

Most likely this a a bug in the REST API. I would recommend opening a ticket.
As a workaround you could create a WebReport that does the same thing / removes a RM Classification from a Node and call that using the REST API.

Regards,
-MC

David Henshaw

@Clarke - using the WR tag above - this would fail, because the expected HTTP Verb is DELETE and the above defaults to GET.

@JeroenL - that API guide I believe is correct. provided you send with DELETE verb and the node ID supplied is RM enabled (classifiable) and you provide a valid RM Classification ID, you should be able to remove. I'd be checking the actual specific version of Content Server you're running - as that API may only be available in later versions. I'm running 25.3 and it's certainly working.

JeroenL

Hi, thank you for your reactions.

It Seems all DELETE methods are not working.

We run OpenText Content Server 25.2, build 16.2.32.5895 and use the correct version of the RestAPI documentation.

Http methods that use GET, PUT and POST work correctly.

But methods that uses DELETE do not work.

for example:

HttpRequestMessage(HttpMethod.Delete, $"/v2/nodes/{docID}/versions"); does not work.

In de IIS logging I get the error log:

2025-11-18 11:17:26 10.10.80.58 DELETE /v2/nodes/11127839/versions - 443 - 10.0.40.55 - - 404 0 2 3

I have tried some settings in IIS but non so far seem to be able to fix this issue.

David Henshaw

Very odd.

If all APIs that use DELETE verb are responding with a 404, that's indeed odd. My first inclination here would be to check the web server configuration and verify that it is not doing any request filtering on the verb. Perhaps IIS request filtering is precluding those requests getting through

Clarke

I have seen this before. Sometimes IIS blocked the Delete verb.
You can check out this part of IIS

Regards,
-MC

Clarke

All WR are gets. You "call" the WR with a GET but the WR runs Delete code / whatever you put in the WR.
This would 100% work.

Regards,
-MC

JeroenL

2025-11-19_17-11-58.png

Thank you for your response. Unfortunately that alone is not the solution. I already had added the DELETE verb. to be allowed.

JeroenL

Is seems I have made a typo:

I used the adress: v2/nodes/{docID}/versions

But that should have been: api/v2/nodes/{docID}/versions

All is working correctly now.