Are you sure there is a document ID 1234?
I think that with the v3 API, the ID it's looking for isn't the document ID you see in the URL - it's a different ID that's unique across all content types. If you know the object type and object ID (from the URL), you can make a query like this:
and in the JSON results, look for the "self" link. That will contain the unique content ID in it.
The object type for documents is 102 - you can find all the values in the JiveObejctType table.
We're also using "self" link to get it. But we would also wanna there is any other good approach. Thank you very much.
My guess is that you are using a Document ID (i.e. /docs/DOC-1234) and passing that into the /contents service as the Content ID. If that is the case, then you are unfortunately using the wrong ID.
If you wanted to get this resource, you would need to use an Entity Descriptor filter that uses these native ids, such as:
In this case, 102 = Document Content Type.
Hope this helps,
Ryan, You're correct. We used a wrong document ID as content ID and Gregory provided us a good solution and it works now. Thank you very much.